ISTQB Test Analysis and Design: In the ISTQB syllabus, the Test Process consists of a five phases Plan, Design, Implement/Execute, Report, Closure. (Our blog titled “Software Test Life Cycle” has more details .) The second phase of the Software Test Life Cycle is Test Analysis and Design, where specifications are analysed and test cases designed. This […]
Read MoreWhen we log defects there are two fields that we need to fill in – Severity and Priority. In this blog, we look at the differences between these and some typical scenarios. Defect Severity: This stands for the degree of impact the defect can have on testing and user’s needs. High – showstopper, tester/user cannot […]
Read MoreWe have seen the Software Development Life Cycle in one of our previous blogs. V-model, Iterative models are examples of how software can be developed. The Software Test Life Cycle is a part of the Software Development Life Cycle. And the Test Life Cycle is used for System Testing and for User Acceptance Testing. The […]
Read MoreDefects: Defects are the most visible part of the Software Test Process. Defects found in Production/Live environment and by customer are termed ‘Failures’. Any testing team is evaluated by the number found during testing and the failures encountered by the customer. If the customer encounters a vast number of failures, the efficacy of the testing […]
Read MoreUser Acceptance Testing (UAT): We have so far in our blogs looked at Unit testing, Integration testing and System testing in detail. In today’s blog, we take a look at User Acceptance Test or UAT for short. UAT comes after System testing. Though the application has undergone these different tests, the customer (the king/queen) has […]
Read MoreSystem Testing or Functional Testing: System Testing is the next level of testing after Unit and Integration Testing. In System testing, end to end testing is conducted in an environment representative of the live or production environment. The test cases are based completely on the Functional Specification. And an independent test team(independent of the development […]
Read MoreIntegration strategy stands for HOW individual modules will be combined during Integration testing. The individual modules can be combined in one go, or they can be joined one by one. A decision on how to put the pieces together is called the Integration Strategy. There are 3 strategies – Big Bang, Top Down Integration & […]
Read MoreTests conducted by Developers: In our blog on V-model, we looked at how for every phase in the SDLC, a corresponding testing activity was introduced. So we have Unit Testing, Integration Testing, System Testing and User Acceptance Testing. Of these, the Unit Testing and Integration Testing are primarily the responsibility of the Development team. The […]
Read MoreDifferent Types of ISTQB Testing: A Comprehensive Guide In today’s rapidly developing software development, the importance of delivering high-quality software products cannot be overstated. Professionals in the field use a variety of testing methodologies to achieve effective software quality assurance. One widely acknowledged framework in this domain is the International Software Testing Qualifications Board (ISTQB), […]
Read MoreTest Levels: In our previous blog we understood how the V-model extends the waterfall model with the testing activities that need to be completed later in SDLC. And for every development activity, we saw a corresponding testing activity. And how the test phase for a given level began during the corresponding software development activity. During the Requirements […]
Read More
