 Hello, Myself M. V. Bhogade, assistant professor of CAC department from WIT, Sholapur. In this session, we are going to see some points from low testing, stress testing, integration testing. So, these are the learning outcomes that is at the end of this session, student will be able to understand low testing, stress testing and integration testing. So, these are the contents for today's session. Do you know that low testing is a type of non-functional testing? Low testing is commonly used for the client server web based applications, both intranet and internet. So, what is low testing? It is a kind of performance testing which determines a system's performance under real life conditions. This testing helps determine how the application behaves when multiple users access it simultaneously. It usually identifies the maximum operating capacity of an application, determine whether current infrastructure is sufficient to run the application, sustainability of application with respect to peak user load, number of concurrent user that an application can support and scalability to allow more users to access it. So, why should we use low testing? It gives confidence in the system and its reliability and performance. It helps identify the bottlenecks in the system under heavy user stress scenarios before they happen in a production environment. It gives excellent protection against poor performance and accommodates complementary strategies for performance management and monitoring of production environment. So, goals of low testing is response time for each transaction, performance of system components under various loads, performance of database components under different loads, network delay between the client and server, software design issues, server configuration issues like web server, application server, database server, etc. Hardware limitation issues like CPU maximization, memory limitizations, network bottlenecks, etc. Strategies of low testing are manual load testing in-house developed load testing tools, open source load testing tools, enterprise class load testing tools. Guidelines for load testing are, load testing should be planned once the application becomes functionally stable. Large number of unique data should be ready in the data pool. Number of users should be dedicated for each scenario or scripts. Avoid creation of detailed logs to conserve the disk IO space. Try to avoid downloading of images in the site. Consistency of response time over lapsed period should be logged and the same should be compared with various test runs. The tools are Neo load, load view, load runner, web load. Advantages are performance bottlenecks, identification view for production, improves the scalability of the system, minimize risk related to system downtime, reduced costs of failure, increased customer satisfaction, disadvantage are need programming knowledge to use load testing tools, tools can be expensive as pricing depends on the number of virtual user supported. So, think an answer, load testing is commonly used for, the answer is, it is commonly used for client, server, web based applications both intranet and internet. So, stress testing, so what is stress testing? It is used to test the scalability and reliability of the system. This test mainly determines the system on its robustness and error handling under extremely heavy load conditions. Stress testing is done to make sure that the system would not crash under crunch situations. Stress testing is also known as endurance testing. Example is suppose if I copy 5GB of data from the website and paste into a notepad. So, usually in notepad we paste 2KB or 20KB of data. But if I paste 5GB of data, the notepad will give you error. That is notepad is under stress and it is not responded error. Goals are the goal of stress testing is to analyze the behavior of the system after failure for stress testing to be successful. System should display appropriate error message while it is under extreme conditions. The main purpose of stress testing is to make sure that the system requires after failure which is called a recoverability. Types of stress testing are distributed stress testing, application stress testing, transactional stress testing, systematic stress testing, exploratory stress testing. Tools recommended for stress testing are load runner, jmeter, stress tester, neo load. Metrics for stress testing are measuring scalability and performance. Page per second that is measures how many pages have been requested per second. Throughput basic metric response data size per second. Rounds number of times test scenarios has been planned versus number of times client has executed. Second is application response hit time. Average time to retrieve an image or a page. Time to the first byte that is time taken to return the first byte of data or information. Page time. Time taken to retrieve all information in a page. Failures. Failure failed connections. Number of failed connections refused by the client that is weak signal. Failed rounds. Number of rounds it gets failed. Failed hits. Number of failed attempts done by the system broken links or unseen images. Now we will see integration testing. So here individual software modules are integrated logically and tested as a group. A typical software project consists of multiple software modules coded by different programmers. Integration testing focuses on checking data communication among these modules. Hence it is also termed as I and T that is integration and testing, string testing and sometimes thread testing. So why should we do integration testing? Although each software module is unit tested, defects still exist for various reasons like integration testing becomes necessary to verify the software modules work in unity. As modules are designed by individual software developer, at the time of module development there are wide chances of change in requirements by the clients. These new requirements may not be unit tested and hence system integration testing becomes necessary. Interfaces of the software modules with the database could be erroneous. External hardware interfaces if any could be erroneous. Inadequate exception handling could cause issues. Integration testing procedure. Prepare the integration test plans. Design the test scenario case and scripts. Executing the test cases followed by reporting the defects. Tracking and read testing the defects. Step number three and four are repeated until the completion of integration is successfully. Now entry and exit criteria. So entry criteria is unit tested components or modules. All high prioritized bugs fixed and closed. All modules to be coded completely and integrated successfully. Integration test plan, test case scenarios to be signed off and documented. Required test environment to be set up for integration testing. Exit criteria. Successful testing of integrated application. Executed test cases are documented. All high prioritized bugs fixed and closed. Technical documents to be submitted followed by release notes. So these are the references from where we have taken the help like software testing, genius or guru99.com and all. So from here we have taken the reference. Thank you.