- Purpose of the test
- Software requirements and Hardware requirements (if any)
- Specific setup or configuration requirements
- Description on how to perform the test(s)
- Expected results or success criteria for the test
Tuesday, June 1, 2010
Designing a Test Case
Test cases should be designed and written by someone who understands the function or technology being tested. A test case should include the following information -
Test Case Structure
A formal written test case comprises of three parts -
- Information
Information consists of general information about the test case. Information incorporates Identifier, test case creator, test case version, name of the test case, purpose or brief description and test case dependencies. - Activity
Activity consists of the actual test case activities. Activity contains information about the test case environment, activities to be done at test case initialization, activities to be done after test case is performed, step by step actions to be done while testing and the input data that is to be supplied for testing. - Results
Results are outcomes of a performed test case. Results data consist of information about expected results and the actual results.
Test Case
A test case is a set of conditions or variables and inputs that are developed for a particular goal or objective to be achieved on a certain application to judge its capabilities or features.
It might take more than one test case to determine the true functionality of the application being tested. Every requirement or objective to be achieved needs at least one test case. Some software development methodologies like Rational Unified Process (RUP) recommend creating at least two test cases for each requirement or objective; one for performing testing through positive perspective and the other through negative perspective.
It might take more than one test case to determine the true functionality of the application being tested. Every requirement or objective to be achieved needs at least one test case. Some software development methodologies like Rational Unified Process (RUP) recommend creating at least two test cases for each requirement or objective; one for performing testing through positive perspective and the other through negative perspective.
Monday, May 31, 2010
Software Testing Life Cycle
Software testing life cycle identifies what test activities to carry out and when (what is the best time) to accomplish those test activities. Even though testing differs between organizations, there is a testing life cycle.
Software Testing Life Cycle consists of six (generic) phases:
Software Testing Life Cycle consists of six (generic) phases:
- Test Planning,
- Test Analysis,
- Test Design,
- Construction and verification,
- Testing Cycles,
- Final Testing and Implementation and
- Post Implementation.
Software Testing Life Cycle | ||
---|---|---|
Phase | Activities | Outcome |
Planning | Create high level test plan | Test plan, Refined Specification |
Analysis | Create detailed test plan, Functional Validation Matrix, test cases | Revised Test Plan, Functional validation matrix, test cases |
Design | test cases are revised; select which test cases to automate | revised test cases, test data sets, sets, risk assessment sheet |
Construction | scripting of test cases to automate, | test procedures/Scripts, Drivers, test results, Bugreports. |
Testing cycles | complete testing cycles | Test results, Bug Reports |
Final testing | execute remaining stress and performance tests, complete documentation | Test results and different metrics on test efforts |
Post implementation | Evaluate testing processes | Plan for improvement of testing process |
Tuesday, April 27, 2010
Thursday, April 22, 2010
How software testing can be stated as the process of validation and verification?
Validation is to identify wether the system is build according to user requirementsand fit for the purpose or we building the rite system.
Are we building the rite system is verification.
And stated as process of validating verifying that a software, program,application,product:
meets business and technical requirements.
Are we building the rite system is verification.
And stated as process of validating verifying that a software, program,application,product:
meets business and technical requirements.
Tuesday, March 9, 2010
Why Test..?
In order to find Bugs in a product.
To Give a good quality product.
The Effect of testing is to indication of Software Quality.
Build Confidence.
Reduce costs.
Show the system meet user needs.
Asses the software quality
To Give a good quality product.
The Effect of testing is to indication of Software Quality.
Build Confidence.
Reduce costs.
Show the system meet user needs.
Asses the software quality
Subscribe to:
Posts (Atom)