Test management tools

These are some of the tools that are used to plan, manage and track the testing activities, with their corresponding vendors such as:

1) Test director
2) Test Manager
3) QA Director

Automated testing tools

1) Quick Test Professional :-Functional and Regression.
2) Silk Performer : -Load, Stress and Performance .
3) Silk Test :- Functional and Regression .
4) WinRunner 6.2 :- Functional and Regression.
5) Test director :- Effective test management.
6) Rational Robot :- GUI .
7) Rational suite Test Studio:- Functional and test control.
8) Rational Rose :- Unit / Design changes and reengineering.
9) QA Wizard :- Web based applications or Web sites, Windows applications, or Java applications.

Automation Testing life cycle

1) QA costs High Quality to market
2) Low Time to market
3) Reduced testing time
4) Consistent test procedures
5) Reduced
6) Improved testing productivity
7) Improved product quality

AST Requirements
• Requirement / Functional Specification documents• Design Specification documents (use cases, etc)• Test Traceability Matrix for identifying Test Coverage• Functional/ Non-Functional and test data requirements• Test phases to be automated and % of automation

AST Environment Setup
• AST Test Bed installation and configuration• Network connectivity’s• All the Software/ tools Licenses, Installation and configuration• Coordination with Vendors and others

AST Design
• Test Script and test data preparation• Test scripts / test data review and unit testing• Integration Testing Test scripts and testing• Base lining under Configuration Management

AST Execution and Defect Tracking
• Executing AST Test Suit• Capture, review and analyze Test Results• Defects reporting and tracking for its closure

AST Maintenance Reports and Acceptance
• AST Results and summary reports• Test Metrics and process Improvements made• Base lining of AST Test suits/ scripts/ test date etc for maintenance phase• Getting Acceptance

Test development life cycle

1) Requirements
2) Use Case Document
3) Test Plan
4) Test Case
5) Test Case execution
6) Report Analysis
7) Bug Analysis
8) Bug Reporting

Typical interaction scenario from a user's perspective for system requirements studies or testing. In other words, "an actual or realistic example scenario". A use case describes the use of a system from start to finish. Use cases focus attention on aspects of a system useful to people outside of the system itself.
Users of a program are called users or clients. Users of an enterprise are called customers, suppliers, etc.Use Case:
A collection of possible scenarios between the system under discussion and external actors, characterized by the goal the primary actor has toward the system's declared responsibilities, showing how the primary actor's goal might be delivered or might fail.
Use cases are goals (use cases and goals are used interchangeably) that are made up of scenarios. Scenarios consist of a sequence of steps to achieve the goal, each step in a scenario is a sub (or mini) goal of the use case. As such each sub goal represents either another use case (subordinate use case) or an autonomous action that is at the lowest level desired by our use case decomposition
This hierarchical relationship is needed to properly model the requirements of a system being developed. A complete use case analysis requires several levels. In addition the level at which the use case is operating at it is important to understand the scope it is addressing. The level and scope are important to assure that the language and granularity of scenario steps remain consistent within the use case
Scopes:Strategic and System
Strategic Scope:-The goal (Use Case) is a strategic goal with respect to the system. These goals are goals of value to the organization. The use case shows how the system is used to benefit the organization.,/p> These strategic use cases will eventually use some of the same lower level (subordinate) use cases.
System Scope:-Use cases at system scope are bounded by the system under development. The goals represent specific functionality required of the system. The majority of the use cases are at system scope. These use cases are often steps in strategic level use cases

Mercury TestDirector

1)Can you estimate efforts required to fully test requirements and make informed decisions regarding effort and risk tradeoffs?
2)Does your organization lack the software testing tools to deploy high-quality applications quickly and effectively?
3)Does your organization have the appropriate level of communication, organization, documentation, and structure in place for every testing project?
4)Do you have a consistent, repeatable testing process?
Are you able to track application release progress and project tasks?

Mercury TestDirector™ for Quality Center allows you to deploy high-quality applications quickly and effectively by providing a consistent, repeatable process for gathering requirements, planning and scheduling tests, analyzing results, and managing defects and issues. TestDirector is a single, web-based application for all essential aspects of test management — Requirements Management, Test Plan, Test Lab, and Defects Management. You can leverage these core modules either as a standalone solution or integrated within a global Quality Center of Excellence environment.

With Mercury TestDirector for Quality Center, you can:

• Proactively track the progress of releases and cycles so your organization can make more informed budgetary and release decisions and have the ability to analyze, evaluate, and improve your current processes over the lifetime of the application.
• Perform risk-based quality management enabling you to create appropriate test strategies by calculating test requirements against business risk levels and available resources
• Facilitate information access across geographical and organization boundaries by supporting high levels of communication and collaboration among IT teams.
• Get real-time visibility for inter-related quality assets allowing you to test only what’s been impacted, giving you the time to run a full regression test after each change.

What is black box/white box testing

Black-box and white-box are test design methods. Black-box test designtreats the system as a "black-box", so it doesn't explicitly useknowledge of the internal structure. Black-box test design is usuallydescribed as focusing on testing functional requirements. Synonyms forblack-box include: behavioral, functional, opaque-box, andclosed-box. White-box test design allows one to peek inside the "box",and it focuses specifically on using internal knowledge of the softwareto guide the selection of test data. Synonyms for white-box include:structural, glass-box and clear-box.

While black-box and white-box are terms that are still in popular use,many people prefer the terms "behavioral" and "structural". Behavioraltest design is slightly different from black-box test design becausethe use of internal knowledge isn't strictly forbidden, but it's stilldiscouraged. In practice, it hasn't proven useful to use a single testdesign method. One has to use a mixture of different methods so thatthey aren't hindered by the limitations of a particular one. Some callthis "gray-box" or "translucent-box" test design, but others wish we'dstop talking about boxes altogether.

It is important to understand that these methods are used during thetest design phase, and their influence is hard to see in the tests oncethey're implemented. Note that any level of testing (unit testing,system testing, etc.) can use any test design methods. Unit testing isusually associated with structural test design, but this is becausetesters usually don't have well-defined requirements at the unit levelto validate.

Welcome

Hi i am Abdhesh kumar Upadhyay