Software Testing -|Levels Lavals of Testing Test Individual Component Test IntegratedComponent Test the entire System Perce reed LSI) test the final System Pts by * This type of testing is performed by developers before the setup is handed over to the testing team to formally execute the test cases. * It is performed on the individual units of source code assigned areas. *It is a level of the software testing process where individual units/components of a sofiware/system are tested. + The goal of unit testing is to isolate each part of the program and show that individual parts are correct in terms of requirements and functionality * After having exhausted all the options, there is no choice but to stop unit testing and merge the code segment with other units,Mrseeest ue Meat re RE In Integration testing process where individual units are combined and tested as a group. +The purpose of this level of testing is to expose faults in the interaction between integrated units. + Integration testing can be done in three ways: > Bottom-up integration testing > Top-down integration testing » Big Bang integration testing Integration Testing Method RE * Bottom-up integration Testing is an approach where bottom level units are tested first and after that upper-level units are tested step by step. ‘toa + Top-down integration, In this testing. the highest-level modules are tested first and progressively. lower-level modules are tested —thereaflerMethod + Big Bang is an approach where all or most of the units are combined together and tested at one go. This approach is taken when the testing team receives the entire software in a bundle. Integration Testin Note:-In a comprehensive software development environment, bottom-up testing is usually done first, followed by top-down testing. ystem Testing + In system testing process a complete, integrated system/software is tested + Once all the components are integrated. the application as a whole is tested to see that it meets the specified Quality Standards. + This type of testing is performed by a specialized testing team. * System testing is the first step in the SDLC, where the application is tested as a whole. +The application is tested thoroughly to verify that it meets the functional and technical specifications.System! Testing JRE + The application is tested in an environment that is very close to the production environment where the application will be deployed. * System testing enables us to test. verify, and validate both the business requirements as well as the application architecture. +For example, a system test might involve testing a login interface, then creating and editing an entry, plus sending or printing results, followed by summary processing or deletion (or archiving) of entries, then logoff. Acceptance Testing RE +A level of the software testing process where a system is tested for acceptability. + Commonly this level of Acceptance testing include the following four types: > User acceptance testing > Operational acceptance testing > Contractual and regulatory acceptance testing > Alpha and beta testingAcceptance Testing JRE + Acceptance testing performed by the customer. often in their lab environment on their own hardware is known as User acceptance testing. + Operational acceptance is used to conduct operational readiness (pre-release) of a product. service or system as part of a quality management system. *It is conducted by the Quality Assurance Team who will test whether the application meets the intended specifications and satisfies the client's requirement. * The QA team will have a set of pre-written scenarios and test cases that will be used to test the ‘application, eceptance Testing RE * Contractual acceptance testing is performed based on the contract's acceptance criteria defined during the agreement of the contract. while regulatory acceptance testing is performed based on the relevant regulations to the software product.Alpha Testing JRE *Alpha testing is testing of an application when development is about to complete, Minor changes can still be made as a result of alpha testing. p> Pes Alpha testing is a type of acceptance testing: performed to identify all possible issues/bugs before releasing the product to real users . PME od ae Velie tele po IRE * This is a form of internal acceptance testing. + This testing uses both black box and white box techniques. + Alpha testing is carried out in a lab environment and usually done by the testers are internal employees of the organization.Beta Testing (pre-release testing) ¥ Et *Beta Testing is performed by real users of the software application in a real environment and can be considered as a form of external User Acceptance Testing. * Beta version of the software is released to a limited number of end-users of the product to obtain feedback on the product quality. * It is the final test before shipping a product to the customers. «Direct feedback from customers is a major advantage of Beta Testing. Beta Testing... JRE + Fixing the issues in the beta release can significantly reduce the development cost as most of the minor glitches get fixed before the final release. * Until now many big companies have successfully used beta versions of their most anticipated applications. + Example, Microsoft Corporation released Windows 10 beta and based on the feedback from thousands of users they managed to release a stable OS version. + In the past. Apple also released OS X beta in public and fixed many minor issues and improved the OS based on user feedback.Beta Testing... +The selection of beta test groups can be done based on the company's needs. The company can either invite few users to test the preview version of the application or they can release it openly to give it a try by any user. Pea stele mr nia) :4 Alph E Performed at developer's site - testing Performed in real environment, and hence ‘environment. Hence, the activities can be activities cannot be controlled. controlled. Issues Bugs are logged into the identified Issues Bugs are collected fiom real users in the tool directly and are fixed by developer at form of suggestions feedbacks and are considered high priority as improvements for future releases. ‘Toevaluate the quality of the product, To evaluate customer satisfaction. Implemented after System testing phase Implemented after Alpha Testing and product is or when the product is 70% - 90% 90% 95% complete, complete.Alpha Vs Beta Testi PE AY eit ig rem tai Focus on finding bugs Focus on collecting — suggestions/ feedback and evaluate them effectively Alpha testing performed by Beta testing is performed by Clients or Testers who are usually internal End Users who are not employees of the employees of the organization organization Alpha testing involves both the Beta Testing typically uses Black Box white box and black box Testing. techniques Types df Beta mesting ME + Traditional Beta testing: Product is distributed to the target market. and related data is gathered in all aspects. This data can be used for Product improvement. + Public Beta Testing: Product is publicly released to the outside world via online channels and data can be gathered from anyone. Based on feedback. product improvements can be done. + Technical Beta Testing: Product is released to the internal group of an organization and gathers feedback/data from the employees of the organization.Types of Beta desting RE “Focused Beta: Product is released to the market for gathering feedback on specific features of the program. Example. important functionality of the software. +Post-release Beta: Product is released to the market and data is gathered to make improvements for the future release of the product.