SOFTWARE TESTING.pptx
- 2. Software Testing Software testing is a process of identifying the correctness of software by considering its all attributes (Reliability, Scalability, Portability, Re-usability, Usability) and evaluating the execution of software components to find the software bugs or errors or defects.
- 3. Software testing provides an independent view and objective of the software and gives surety of fitness of the software. It involves testing of all components under the required services to confirm that whether it is satisfying the specified requirements or not. The process is also providing the client with information about the quality of the software. Testing is mandatory because it will be a dangerous situation if the software fails any of time due to lack of testing. So, without testing software cannot be deployed to the end user.
- 4. Testing is a group of techniques to determine the correctness of the application under the predefined script but, testing cannot find all the defect of application. The main intent of testing is to detect failures of the application so that failures can be discovered and corrected. It does not demonstrate that a product functions properly under all conditions but only that it is not working in some specific conditions. Testing furnishes comparison that compares the behavior and state of software against mechanisms because the problem can be recognized by the mechanism. The mechanism may include past versions of the same specified product, comparable products, and interfaces of expected purpose, relevant standards, or other criteria but not limited up to these.
- 5. Testing includes an examination of code and also the execution of code in various environments, conditions as well as all the examining aspects of the code. In the current scenario of software development, a testing team may be separate from the development team so that Information derived from testing can be used to correct the process of software development. The success of software depends upon acceptance of its targeted audience, easy graphical interface, strong functionality load test, etc. For example, the audience of banking is totally different from the audience of a video game. Therefore, when an organization develops a software product, it can assess whether the software product will be beneficial to its purchasers and other audience.
- 6. The different types of Software Testing The categorization of software testing is a part of diverse testing activities, such as Test Strategy, Test Deliverables, A Defined Test Objective, Etc. And software testing is the execution of the software to find defects. The purpose of having a testing type is to confirm the AUT (Application Under Test). To start testing, we should have a requirement, application-ready, necessary resources available. To maintain accountability, we should assign a respective module to different test engineers. The software testing mainly divided into two parts, which are as follows:
- 9. Type of Software testing
- 11. Manual Testing Testing any software or an application according to the client's needs without using any automation tool is known as manual testing. It is a procedure of verification and validation. Manual testing is used to verify the behavior of an application or software in contradiction of requirements specification Do not require any precise knowledge of any testing tool to execute the manual test cases. We can easily prepare the test document while performing manual testing on any application.
- 12. Classification of Manual Testing
- 13. White Box Testing In white-box testing, the developer will inspect every line of code before handing it over to the testing team or the concerned test engineers. Subsequently, the code is noticeable for developers throughout testing; that's why this process is known as WBT (White Box Testing). The developer will execute the complete white-box testing for the particular software and send the specific application to the testing team. The purpose of implementing the white box testing is to emphasize the flow of inputs and outputs over the software and enhance the security of an application. White box testing is also known as open box testing, glass box testing, structural testing, clear box testing, and transparent box testing.
- 14. White box testing which also known as glass box is testing, structural testing, clear box testing, open box testing and transparent box testing. It tests internal coding and infrastructure of a software focus on checking of predefined inputs against expected and desired outputs. It is based on inner workings of an application and revolves around internal structure testing. In this type of testing programming skills are required to design test cases. The primary goal of white box testing is to focus on the flow of inputs and outputs through the software and strengthening the security of the software. The term 'white box' is used because of the internal perspective of the system. The clear box or white box or transparent box name denote the ability to see through the software's outer shell into its inner workings. Developers do white box testing. In this, the developer will test every line of the code of the program. The perform the White-box testing and then send the application or the software to the testing team, where they will perform the black box testing and verify the application along with the requirements and identify the bugs and sends it to the developer. The developer fixes the bugs and does one round of white box testing and sends it to the testing team. Here, fixing the bugs implies that the bug is deleted, and the particular feature is working fine on the application.
- 15. The test engineers will not include in fixing the defects for the following reasons: • Fixing the bug might interrupt the other features. Therefore, the test engineer should always find the bugs, and developers should still be doing the bug fixes. • If the test engineers spend most of the time fixing the defects, then they may be unable to find the other bugs in the application.
- 16. The white box testing contains various tests, which are as follows: White Box Testing •Path testing •Loop testing Condition testing •Testing based on the memory perspective •Test performance of the program
- 17. Path Testing In the path testing, the flow graphs and test all independent paths. Here writing the flow graph implies that flow graphs are representing the flow of the program and also show how every program is added with one another. And test all the independent paths implies that suppose a path from main() to function G, first set the parameters and test if the program is correct in that particular path, and in the same way test all other paths and fix the bugs.
- 18. Loop testing In the loop testing, test the loops such as while, for, and do-while, etc. and also check for ending condition if working correctly and if the size of the conditions is enough. For example: one program where the developers have given about n no. of loops. We cannot test this program manually for all the n loops cycle. So we write a small program that helps for all n cycles.
- 19. Condition testing This test all logical conditions for both true and false values; that is, it will verify for both if and else condition.
- 20. Testing based on the memory (size) perspective The size of the code is increasing for the following reasons: • The reuse of code is not there: let us take one example, where we have four programs of the same application, and the first ten lines of the program are similar. We can write these ten lines as a discrete function, and it should be accessible by the above four programs as well. And also, if any bug is there, we can modify the line of code in the function rather than the entire code. • The developers use the logic that might be modified. If one programmer writes code and the file size is up to 250kb, then another programmer could write a similar code using the different logic, and the file size is up to 100kb. • The developer declares so many functions and variables that might never be used in any portion of the code. Therefore, the size of the program will increase.
- 22. Test the performance (Speed, response time) of the program The application could be slow for the following reasons: • When logic is used. • For the conditional cases, use or & and adequately. • Switch case, which means we cannot use nested if, instead of using a switch case. The developer is performing white box testing, they understand that the code is running slow, or the performance of the program is also getting deliberate. And the developer cannot go manually over the program and verify which line of the code is slowing the program. To recover with this condition, a tool called Rational Quantify, which resolves these kinds of issues automatically. Once the entire code is ready, the rational quantify tool will go through the code and execute it. And we can see the outcome in the result sheet in the form of thick and thin lines.
- 23. Here, the thick line specifies which section of code is time-consuming. When we double-click on the thick line, the tool will take us to that line or piece of code automatically, which is also displayed in a different color. We can change that code and again and use this tool. When the order of lines is all thin, we know that the presentation of the program has enhanced. And the developers will perform the white box testing automatically because it saves time rather than Thin Line Thick Line
- 24. Generic steps of white box testing • Design all test scenarios, test cases and prioritize them according to high priority number. • This step involves the study of code at runtime to examine the resource utilization, not accessed areas of the code, time taken by various methods and operations and so on. • In this step testing of internal subroutines takes place. Internal subroutines such as nonpublic methods, interfaces are able to handle all types of data appropriately or not. • This step focuses on testing of control statements like loops and conditional statements to check the efficiency and accuracy for different data inputs. • In the last step white box testing includes security testing to check all possible security loopholes by looking at how the code handles security. Reasons for white box testing • It identifies internal security holes. • To check the way of input inside the code. • Check the functionality of conditional loops. • To test function, object, and statement at an individual level.
- 25. Advantages of White box testing • White box testing optimizes code so hidden errors can be identified. • Test cases of white box testing can be easily automated. • This testing is more thorough than other testing approaches as it covers all code paths. • It can be started in the SDLC phase even without GUI. Disadvantages of White box testing • White box testing is too much time consuming when it comes to large-scale programming applications. • White box testing is much expensive and complex. • It can lead to production error because it is not detailed by the developers. • White box testing needs professional programmers who have a detailed knowledge and understanding of programming language and implementation.