Month: June 2012

Performance testing with pyUnitPerf

Summary: If you are familiar with Mike Clark‘s JUnitPerf framework, then you may be interested in knowing that I have just released a Python port: pyUnitPerf. You can browse the source code here and you can get a gzipped tarball from here.Details pyUnitPerf tests are meant to transparently add performance testing capabilities to existing pyUnit test suites. The pyUnitPerf framework introduces 2 new types of tests: TimedTest: runs an existing pyUnit test case by imposing a limit to the time it takes to run the test LoadTest: runs an existing pyUnit test case by simulating concurrent users and iterations Let’s Read More

V Model to W Model | W Model in SDLC Simplified

We already discuss that V-model is the basis of structured testing. However, there are a few problems with V Model. V Model Represents one-to-one relationship between the documents on the left-hand side and the test activities on the right. This is not always correct. System testing not only depends on Function requirements but also depends on technical design, architecture also. A couple of testing activities are not explained in the V model. This is a major exception and the V-Model does not support the broader view of testing as a continuously major activity throughout the Software development lifecycle.   Paul Read More

V-model is the basis of structured testing

You will find out this is a great model! V-model is the basis of structured testing The left side shows the classic software life cycle & the Right side shows the verification and validation for Each Phase Analyze User requirements End users express their wish for a solution for one or more problems they have. In testing, you have to start preparing for your user tests at this moment! You should do test preparation sessions with your acceptance testers. Ask them what causes they want to test. It might help you to find good test cases if you interview end-users Read More

Art of Test case writing

Objective and Importance of a Test Case – The basic objective of writing test cases is to ensure complete test coverage of the application.  The most extensive effort in preparing to test software is writing test cases. Gives better reliability in estimating the test effort Improves productivity during test execution by reducing the “understanding” time during execution Writing effective test cases is a skill and that can be achieved by experience and in-depth study of the application on which test cases are being written. Documenting the test cases prior to test execution ensures that the tester does the ‘homework’ and Read More

Testing Stop-Process

This can be difficult to determine. Many modern software applications are so complex and run in such as interdependent environment, that complete testing can never be done. “When to stop testing” is one of the most difficult questions to a test engineer. Common factors in deciding when to stop are:   Deadlines ( release deadlines, testing deadlines.) Test cases completed with certain percentages passed Test budget depleted Coverage of code/functionality/requirements reaches a specified point The rate at which Bugs can be found is too small Beta or Alpha Testing period ends The risk in the project is under an acceptable Read More