Software Testing Concepts

1. Test Deliverables that need to be mentioned in the test plan : Test Deliverables means The documents which are created during the testing process. The documents created during the testing process are : Test Plan  Test Cases Test Scripts Defect/Enhancement Logs Test Reports 2. Input documents that are needed and referred to write a Test Plan : Test plan documents mean a document describing software testing scope and activities. It is the basis for formally testing any software/product in a project. In test planning phase test leader or test manager will create test plan documents. Following documents are needed and referred to write this test plan are Requirement documents: BRS(Business requirement specification)   SRS (System requirement specification) Development plan Document (DPD) The Documents related to the previous version 3. Software Risk Issues : It is also called a Product risk issue. The risk which is going to affect the ...

Test Plan :  A Test Plan is a document describing software testing scope and activities. It is the basis for formally testing any software/product in a project. In test planning phase test leader or test manager will create test plan documents. There are 2 types of test plan document are : MTP (Master test plan): A single high-level test plan for a project/product that unifies all other test plans. STP (System Test Plan): It is also called a Phase test plan. It is nothing but the test plan for each level of testing 17 Attributes of an (IEEE 829) Test Plan Template : Test Plan Identifier: Provide a unique identifier for the test plan document. It also includes the version number also. References: These attributes mention the document which is referred to create the test plan documents. List the related documents, with links to them if available, including the following: Project Plan Configuration Management Plan Introduction: Provide an overview of t...

Usability Testing : Usability testing is a non-functional testing technique that is a measure of how easily the system can be used by end-users. Usability testing is always done to verify how much the application is user-friendly to an end-user. Usability testing is always done to ensure or verify that the GUI is well designed and easily used. Benefits of Usability Testing:  Helps us to learn whether users are able to complete specified tasks successfully or not, If not, what are the roadblocks? Helps us to identify how long it takes to complete specified tasks. Helps us to find out how satisfied users(participants) are with your Web site or other product. Helps us to understand the pain points, so that we can come up with design solutions to improve user performance and satisfaction.

Localization Testing : Localization testing is the software testing process for checking the localized version of a product for that particular culture or locale settings. The areas affected by localization testing are UI and content. Localization testing is performed to verify the quality of a product's localization for a particular target culture/locale and is executed only on the localized version of the product. It is a type of non-functional testing. Whereas Localization is a process of adapting internationalized software for a specific region or language by adding local specific components and translating text. Example: If the project is designed for Tamil Nadu State in India, The designed project should be in the Tamil language, Tamil virtual keyboard should be present, etc. Internationalization Testing :   Internationalization testing is the process of verifying the application under test to work uniformly across multiple regions and cultures. Internatio...

Smoke Testing:  Smoke Testing is done to make sure if the build we received from the development team is testable or not. It is also called as “Day 0” check. It is done at the “build level”. It helps not to waste the testing time to simply testing the whole application when the key features don’t work or the key bugs have not been fixed yet. Here our focus will be on primary and core application workflow.  Smoke Test is done to make sure if the build we received from the development team is testable or not? Smoke Testing is performed by both Developers and Testers. Smoke Testing exercises the entire application from end to end. Smoke Testing, the build may be either stable or unstable Sanity Testing: Sanity Testing is done during the release phase to check for the main functionalities of the application without going deeper. It is also called as a subset of Regression testing. It is done at the “release level”. At times due to release time constraints rigor...

Performance Testing : Performance testing, a non-functional testing technique performed to determine the system parameters in terms of responsiveness and stability under the various workload. Performance testing measures the quality attributes of the system, such as scalability, reliability and resource usage. Performance Testing Techniques: Load Testing: It is the simplest form of testing conducted to understand the behavior of the system under a specific load. Load testing will result in measuring important business-critical transactions and load on the database, application server, etc., are also monitored. Stress Testing: It is performed to find the upper limit capacity of the system and also to determine how the system performs if the current load goes well above the expected maximum. Endurance Testing: Endurance testing is also known as soak testing. It is performed to determine the system parameters under the continuous expected load. During soak tests, the par...

Regression Testing : Regression testing is the process of testing changes to computer programs to make sure that the older programming still works with the new changes. Regression testing is a normal part of the program development process and, in larger companies, is done by code testing specialists. When a bug is fixed by the development team than testing the other features of the applications which might be affected due to the bug fix is known as regression testing. Regression testing is always done to verify that modified code does not break the existing functionality of the application and works within the requirements of the system. What We Do in the Regression Test Rerunning the previously conducted tests. Comparing current results with previously executed test results. There are two types of regression Testing: Regular Regression Testing Final Regression Testing Regular Regression Testing:   A Regular Regression testing is done between test cy...

Static Testing : The process of evaluating the work product to check whether it fulfills the customer's requirement. Am I building the product right? It is also called as verification  Done by manually reading the work product. This process is done by quality assurance. It is process-oriented Presence of defect and their location Technique: Walkthrough Inspection  Review Dynamic Testing : The process to evaluate the end product to check whether it fulfills the customer's requirement. Am I building the right product? It is also called as validation Done by executing the end product  This process is done by quality control.  It is product-oriented Presence of defect and not their location Technique: Unit testing Integration testing      System testing User acceptance testing 

White Box Testing:  White box testing is a testing technique, that examines the program structure and derives test data from the program code. The other names of glass box testing are clear box testing, open box testing, logic-driven testing or path driven testing or structural testing. White Box Testing is the testing of a software solution's internal coding and infrastructure. White box testing is also known as Clear Box testing, Open Box testing, Structural testing, Transparent Box testing, Code-Based testing, and Glass Box testing. Advantages of white-box testing : Code optimization by finding a hidden error White box tests cases can be easily automated. Disadvantages of white-box testing:    White box testing can be quite complex and expensive.  White box testing requires professional resources, with a detailed understanding of programming and implementation Black box Testing: Black-box testing is a method of software testing that e...