Types and levels of testing chpter 2 (1).pdf
- 1. Unit 2 Marks 18 Types and levels of testing
- 2. 2.1 Levels of testing In general, there are four levels of testing: unit testing, integration testing, system testing, and acceptance testing. The purpose of Levels of testing is to make software testing systematic and easily identify all possible test cases at a particular level.
- 3. 2.2 unit testing • Unit testing focuses verification effort on the smallest unit of software design—the software component or module. Using the component-level design description as a guide, important control paths are tested to uncover errors within the boundary of the module.
- 4. Video lecture on • Unit testing :
- 5. The relative complexity of tests and the errors those tests uncover is limited by the constrained scope established for unit testing. The unit test focuses on the internal processing logic and data structures within the boundaries of a component. This type of testing can be conducted in parallel for multiple components.
- 6. Stubs and drivers These dummy pieces of code are the stubs. On the other hand, Drivers are the ones, which are the "calling" programs. Drivers are used in bottom up testing approach. Drivers are dummy code, which is used when the sub modules are ready but the main module is still not ready. ... This dummy code is then called Driver.
- 8. 2.2 Integration testing Integration testing is a systematic technique for constructing the software architecture while at the same time conducting tests to uncover errors associated with interfacing. Correction is difficult because isolation of causes is complicated by the vast expanse of the entire program. Once all the components or modules are working independently, then we need to check the data flow between the dependent modules is known as integration testing.
- 10. • Integration testing • Integration testing is the second level of the software testing process comes after unit testing. In this testing, units or individual components of the software are tested in a group. The focus of the integration testing level is to expose defects at the time of interaction between integrated components or units. • Unit testing uses modules for testing purpose, and these modules are combined and tested in integration testing. The Software is developed with a number of software modules that are coded by different coders or programmers. The goal of integration testing is to check the correctness of communication among all the modules.
- 11. Video lecture on • Integration testing :
- 12. Top down integration Top-down integration testing is an incremental approach to construction of the software architecture. Modules are integrated by moving downward through the control hierarchy, beginning with the main control module Top-down integration.(main program).
- 14. Bottom-up integration Bottom-up integration testing, as its name implies, begins construction and testing with atomic modules (i.e., components at the lowest levels in the program structure). Because components are integrated from the bottom up, the functionality provided by components subordinate to a given level is always available and the need for stubs is eliminated.
- 16. Bi-directional testing There are 2 types of Integration Testing 1) Incremental Integration Testing 2) Non-Incremental Integration Testing.
- 17. After unit testing is completed, developer performs integration testing. It is the process of verifying the interfaces and interaction between modules. While integrating, there are lots of techniques used by developers and one of them is the incremental approach.
- 18. Incremental Testing Methodologies Top down Integration - This type of integration testing takes place from top to bottom. Unavailable Components or systems are substituted by stubs. Bottom Up Integration - This type of integration testing takes place from bottom to top. Unavailable Components or systems are substituted by Drivers. Functional incremental - The Integration and testing takes place on the basis of the functions or functionalities as per the functional specification document.
- 19. Non – incremental integration There are often a tendency to attempt non- incremental integration. In non-incremental integration all components are combined. The entire software programs are tested as a whole. It usually results in to a set of errors. These errors are very difficult to isolate because of large size of program (due to big bang). Once these errors are corrected new ones appear and this process continues like a end less loop.
- 20. Video lecture on • Software testing STLC:
- 21. 2.3 Testing on web application Web application is a bit different and complex to test as tester don’t have that much control over the application. Application is loaded on the server whose location may or may not be known and no exe is installed on the client machine, you have to test it on different web browsers
- 22. Video lecture on • Web – Application testing :
- 23. Web applications are supposed to be tested on different browsers and OS platforms so broadly Web application is tested mainly for browser compatibility and operating system compatibility, error handling, static pages, backend testing and load testing.
- 24. The applications accessible in browser would be developed in HTML, DHTML, XML, JavaScript etc. (We can monitor through these applications)Applications for the web server would be developed in Java, ASP, JSP, VBScript, JavaScript, Perl, Cold Fusion, PHP etc. (All the manipulations are done on the web server with the help of these programs developed)
- 25. Load testing Load testing is a software testing technique used to examine the behavior of a system when subject to both normal and extreme expected load conditions. Load testing is generally performed under controlled laboratory conditions in order to distinguish between two different systems
- 26. Stress testing Stress testing refers to the testing of software or hardware to determine whether its performance is satisfactory under any extreme and unfavorable conditions, which may occur as a result of heavy network traffic, process loading, underclocking, overclocking(process) and maximum requests for resource utilization.
- 27. Security testing SECURITY TESTING is a type of software testing that intends to uncover vulnerabilities of the system and determine that its data and resources are protected from possible intruders.
- 28. Client server testing In client server application you have two different components to test. Application is loaded on server machine while the application exe on every client machine. You will test broadly in categories like, GUI on both sides, functionality, Load, client-server interaction, backend. This environment is mostly used in Intranet networks. You are aware of number of clients and servers and their locations in the test scenario
- 29. • This type of testing usually done for 2 tier applications (usually developed for LAN) Here we will be having front-end and backend.The application launched on front-end will be having forms and reports which will be monitoring and manipulating data
- 30. Video lecture on • Functional Testing :
- 31. 2.4 Acceptance testing Acceptance testing, a testing technique performed to determine whether or not the software system has met the requirement specifications. The main purpose of this test is to evaluate the system's compliance with the business requirements and verify if it is has met the required criteria for delivery to end users.
- 33. functional test case for amount transfer module
- 35. writing a test case for the ICICI application’s Login module:
- 36. Alpha ,beta testing Alpha testing is a type of acceptance testing; performed to identify all possible issues/bugs before releasing the product to everyday users or public. The focus of this testing is to simulate real users by using black box and white box techniques. The aim is to carry out the tasks that a typical user might perform. Alpha testing is carried out in a lab environment and usually the testers are internal employees of the organization. To put it as simple as possible, this kind of testing is called alpha only because it is done early on, near the end of the development of the software, and before beta testing.
- 37. Beta Testing of a product 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. Beta testing reduces product failure risks and provides increased quality of the product through customer validation.
- 38. GUI testing Success of any GUI application depends on how it interacts with user through its user interface, how the user actions are performed to access application's features and whether application responds in functionally correct manner. An application with incorrect behaviour or invalid user interaction can lead to huge problems. We will try to understand few important aspects with GUI Testing.
- 39. Video lecture on • Regression testing :
- 40. Bloom Level 2 marks question(Knowledge, Remember) Define Unit testing. What is Acceptance Testing . State the Performance Testing. Define stress testing . State the regression testing .
- 41. Understand, Apply level 4 marks Question • Difference between alpha and beta testing . • Explain Incremental and Non-Incremental. • Explain Recovery Testing and Security Testing. • Explain in detail client-server testing. • Describe in detail GUI testing • Explain Bi-Directional integration
- 42. Software Engineering Unit 1 • Objective Question part 1
- 43. Question bank Explain Unit testing? Explain Top-Down integration? Explain Bottom-Up integration? Explain Incremental and Non-Incremental? Explain Bi-Directional integration? Explain Decomposition Based Integration? Explain Recovery Testing and Security Testing? Explain Performance Testing?
- 44. Explain Unit testing in detail? Explain integration in detail? Explain Top-Down Integration? Explain Bottom-Up Integration? Explain Acceptance Testing?
- 45. What is Unit testing? Explain it in detail? What is Integration testing? Explain it in details? What is System testing? Explain it in details? What is Acceptance testing? Explain it in details?
- 46. Question and answer Define Unit Test and characterized the unit test. At a unit test a single component is tested. A unit is the smallest possible testable software component. It can be characterized in several ways A unit in a typical procedure oriented software systems. It performs a single cohensive function. It can be compiled separately. It contains code that can fit on a single page or a screen.
- 47. • Define integration Test. • At the integration level several components are tested as a group and the tester • investigates component interactions. • . Define System test. • When integration test are completed a software system has been assembled and its • major subsystems have been tested. At this point the developers /testers begin to test it • as a whole. System test planning should begin at the requirements phase
- 48. Define Alpha and Beta Test. Alpha test developer’s to use the software and note the problems. Beta test who use it under real world conditions and report the defect to the Developing organization
- 49. • Define functional Testing. • Functional tests at the system level are used ensure that the behavior of the system • adheres to the requirement specifications. • What are the two major requirements in the Performance testing. • Functional Requirement: User describe what functions the software should • perform. We test for compliance of the requirement at the system level with the • functional based system test. • Quality Requirement: They are nonfunctional in nature but describe quality • levels expected for the software
- 50. • What are the steps for top down integration? • Main control module is used as a test driver and stubs are substituted for all • components directly subordinate to the main module. • Depending on integration approach (Depth or breadth first) subordinate stubs are • replaced one at a time with actual components. • Tests are conducted as each component is integrated. • The completion of each set of tests another stub is replaced with real component
- 51. • What is meant by regression testing? • Regression testing is used to check for defects propagated to other modules by • changes made to existing program. Thus, regression testing is used to reduce the side • effects of the changes.
- 52. List the Test plan components. Test plan identifier Introduction Items to be tested Features to be tested Approach Pass/fail criteria Suspension and resumption criteria
- 53. Test deliverables Testing Tasks Test environment Responsibilities Staffing and training needs Scheduling Risks and contingencies Testing costs Approvals.
- 54. • Advantages of Black Box Testing • The test is unbiased because the designer and the tester are independent of each other. • The tester does not need knowledge of any specific programming languages. • The test is done from the point of view of the user, not the designer. • Test cases can be designed as soon as the specifications are complete. • Disadvantages of Black Box Testing • The test can be redundant if the software designer has already run a test case. • The test cases are difficult to design. • Testing every possible input stream is unrealistic because it would take a inordinate amount of time; therefore, many program paths will go untested.