1. TESTING (S,S,AND A,B) By KARTHIKEYAN KANDASAMY

2. TESTING Scenario testing – 1.System & 2. Usecase Defect bash System o Functional and non functional testing Acceptance

3. SCENARIO TESTING Scenario testing is a software testing technique that makes best use of scenarios. Scenarios help a complex system to test better where in the scenarios are to be credible which are easy to evaluate. Methods in Scenario Testing: 1.System scenarios 2.Use-case and role-based scenarios

5. DEFECT BASH Defect bash (or bug bash) is a testing event where a group of people tries to find as many defects as possible from the software. OR It is an adhoc testing where people performing different role in an organization test the product together at the same time.

6. Enabling people “Cross boundaries and test beyond assigned areas” Bringing different people performing different roles together in the organization for testing—“Testing isn’t for testers alone” Letting everyone in the organization use the product before delivery—“Eat your own dog food” Bringing fresh pairs of eyes to uncover new defects—“Fresh eyes have less bias” Bringing in people who have different levels of product understanding to test the product together randomly—“Users of software are not same” Let testing doesn’t wait for lack of/time taken for documentation—“Does testing wait till all documentation is done?” Enabling people to say “system works” as well as enabling them to “break the system“—”Testing isn’t to conclude the system works or doesn’t work”

7. 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. There are various forms of acceptance testing 1.User acceptance Testing 2.Business acceptance Testing 3.Alpha Testing 4.Beta Testing

8. Acceptance Criteria Acceptance criteria are defined on the basis of the following attributes Functional Correctness and Completeness Data Integrity Data Conversion Usability Performance Timeliness Confidentiality and Availability Installability and Upgradability Scalability Documentation

9. SYSTEM TESTING System Testing (ST) is a black box testing technique performed to evaluate the complete system the system's compliance against specified requirements. In System testing, the functionalities of the system are tested from an end-to-end perspective.

11. ACCEPTANCE TEST PLAN - ATTRIBUTES The Acceptance test plan has the following attributes: 1.Introduction 2.Acceptance Test Category 3.operation Environment 4.Test case ID 5.Test Title 6.Test Objective 7.Test Procedure 8.Test Schedule 9.Resources

12. ACCEPTANCE LIFECYCLE

14. Functional Testing Non- Functional Testing 1. In functional Testing tester tests how well the system performs. 1. In Non-Functional Testing tester tests how well the system responds. 2. Functional Testing is based on client requirements. 2. Non- Functional Testing is based on client expectations. 3. Functional Testing means Testing the application against business requirements. 3. Non- Functional Testing means Testing the application against clients and performance requirements. 4. It is a part of System Testing.4. It is also a part of System Testing 5. Functional Testing Validating the behavior of application. 5. Non- Functional Testing Validating the performance of application. 6. This Testing covers Unit Testing, Integration Testing, Smoke Testing, Sanity Testing, Regression Testing and so on. 6. This Testing covers Load/Performance Testing, Stress/Volume Testing, Security Testing, Installation Testing and so on. 7. It is always concentrating on customer requirements. 7. It is always concentrating on customer expectations. 8. Functional Testing means how is your system is doing. 8. Non- Functional Testing means how well your system is doing example usability, performance and stress testing.

15. A few examples of non-functional testing include the following kinds of tests - Performance Testing Security Testing Usability Testing Reliability and Dependability Testing Endurance testing Load testing Localization testing and Internationalization testing Ergonomics Testing Operational Readiness Testing Installation Testing Configuration Testing Compatibility Testing Interoperability Testing Maintainability Testing Availability Testing Recoverability Testing and Miscellaneous Testing