Category: Uncategorized

Software Testing Checklists

Software QA Testing Checklists Today we bring back to you another quality tool that’s so often under-used that we thought we might rehash details about it within the hope that it regains its lost glory. it’s a ‘Check List’. A Checklist may be a catalog of items/tasks that are recorded for tracking. This list might be either ordered during a sequence or might be haphazard. Checklists are a neighborhood and parcel of our daily lives. We use them in various situations from grocery shopping to having a to-do list for the day’s activities. Testing Checklist Are you getting to start a replacement project for testing? Don’t forget to see this Testing Checklist in each and each step of your Project Life Cycle. The list is usually like the Test plan, it’ll cover all 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

Testing Start Process

Testing is sometimes incorrectly thought of as an after-the-fact activity; performed after programming is done for a product. Instead, testing should be performed at every development stage of the product. Test data sets must be derived and their correctness and consistency should be monitored throughout the development process. If we divide the lifecycle of software development into “Requirements Analysis”, “Design”, “Programming/Construction” and “Operation and Maintenance”, then testing should accompany each of the above phases. If testing is isolated as a single-phase late in the cycle, errors in the problem statement or design may incur exorbitant costs. Not only must the Read More

Operations and Maintenance

Corrections, modifications, and extensions are bound to occur even for small programs and testing is required every time there is a change. Testing during maintenance is termed regression testing. The test set, the test plan, and the test results for the original program should exist. Modifications must be made to accommodate the program changes, and then all portions of the program affected by the modifications must be re-tested. After regression testing is complete, the program and test documentation must be updated to reflect the changes.


Here the main testing points are: – Check the code for consistency with design – the areas to check to include modular structure, module interfaces, data structures, functions, algorithms, and I/O handling. – Perform the Testing process in an organized and systematic manner with test runs dated, annotated, and saved. A plan or schedule can be used as a checklist to help the programmer organize testing efforts. If errors are found and changes made to the program, all tests involving the erroneous segment (including those which resulted in success previously) must be rerun and recorded. – Asks some colleague for Read More


The design document aids in programming, communication, and error analysis, and test data generation. The requirements statement and the design document should together give the problem and the organization of the solution i.e. what the program will do and how it will be done. The design document should contain: Principal data structures. Functions, algorithms, heuristics, or special techniques used for processing. The program organization, how it will be modularized and categorized into external and internal interfaces. Any additional information. Here the testing activities should consist of: – Analysis of design to check its completeness and consistency – the total process Read More

Requirements Analysis

The following test activities should be performed during this stage: 1.1 Invest in analysis at the beginning of the project – Having a clear, concise, and formal statement of the requirements facilitates programming, communication, error analysis, and test data generation. The requirements statement should record the following information and decisions: a. Program function – What the program must do?b. The form, format, data types, and units for input. c. The form, format, data types, and units for output. d. How exceptions, errors, and deviations are to be handled. e. For scientific computations, the numerical method or at least the required Read More