Testing (S/W) concept

Slideshow Transcript

1. Slide 1: Software Testing Concept and Methodologies Rajesh Upadhyay MSc MCA
2. Slide 2: Fundamentals of Software Testing
3. Slide 3: 3 3 NON-IT? IT  Is there any difference when you work for same assignment ??? Software Testing Concepts
4. Slide 4: 4 4 Software/Application??  Group of programs designed for end user using operating system and system utilities.  A self contained program that performs well- defined set of tasks under user control.  Programs, procedures, rules, and any associated documentation pertaining to the operation of a system. Software Testing Concepts
5. Slide 5: 5 5 Evolution of software product  Marketing  Survey is done by marketing people for various product and benchmark the products.  Create MRS( Marketing Requirement survey)  Requirement analysis  Feasibility study (social, economical etc)  investigate the need for possible software automation in the given system.  Domain expert Create URS ( User Requirement specification)  Design  software's overall structure is defined.  Software architecture, interdependence of modules, interfaces, database etc is defined.  System analyst Create SRS( High level design, Low level design etc) Software Testing Concepts
6. Slide 6: 6 6 Evolution of software product( Cont.)  Code Generation  design must be translated into a machine-readable form taking input as SRS.  Done by Team of developers.  Reviews after every 500 lines of code • Code Inspection • Code Walkthrough  Testing  New/patched build is tested by Test engineers for stability of the application.  Maintainence  Software is maintained due to changes ( unexpected values into the system) Software Testing Concepts
7. Slide 7: 7 7 Software development life cycle Ongoing Support Review/Test Requirement Operational Analysis Testing High level Integration design Testing Detailed Unit Testing Specifications Coding Software Testing Concepts
8. Slide 8: 8 8 System An inter-related set of components, with identifiable boundaries, working together for some purpose. Output Input Process Software Testing Concepts
9. Slide 9: 9 9 Analysis  The process of identifying requirements, current problems, constraints ,Opportunities for improvement , timelines and Resources costs . Software Testing Concepts
10. Slide 10: 10 10 Design  The business of finding a way to meet the functional requirements within the specified constraints using the available technology Software Testing Concepts
11. Slide 11: 11 11 Software Development life cycle Phases or stages of a project from inception through completion and delivery of the final product… … and maintenance too! Software Testing Concepts
12. Slide 12: 12 12 Software Development life cycle Three Identifiable Phases: 1. Definition 2. Development 3. Maintenance Software Testing Concepts
13. Slide 13: 13 13 Definition Phase  Focuses on WHAT  What information to be processed?  What functions and performances are desired?  What interfaces are to be established?  What design constraints exists?  What validation criteria are required to define a success system? Software Testing Concepts
14. Slide 14: 14 14 Development Phase  Focuses on  How the database should be designed ?  How the software architecture to be designed ?  How the design will be translated in to a code ?  How testing will be performed ?  Three specific steps in Development Phase are:-  a. Design  b. Coding  c. Testing (ignored due to lack of time, due time to market, additional cost involved, lack of testing requirement understanding etc.) ) Software Testing Concepts
15. Slide 15: 15 15 Maintenance Phase “Maintainability is defined as the ease with which software can be understood, corrected, adapted and enhanced”  Maintenance phase focuses on CHANGE that is associated with  Error correction  Adaptation required as the software environment evolves  Enhancements brought about by changing customer requirements  Reengineering carried out for performance improvements Software Testing Concepts
16. Slide 16: 16 16 SDLC Phases  Identify Problems/Objectives S  Determine information Requirements D  Analyze System needs L  C Design the recommended system  Develop and Document software  Testing the System  Implementation and maintaining the system Software Testing Concepts
17. Slide 17: 17 17 SDLC Phases : Requirement Identification & Analysis Phase • Request for Proposal • Proposal • Negotiation • Contract • User Requirement Specification • Software Requirement Specification Software Testing Concepts
18. Slide 18: 18 18 Software Requirement Specifications IEEE 830 : Software Requirement Specification is a means of translating the ideas in the minds of the clients(the inputs) into a set of formal document (the output) of the requirement phase The Role Bridge the communication gap between the client the user and the developer Software Testing Concepts
19. Slide 19: 19 19 SDLC Phases- Design High Level Design  HLD Document contains items in a macro level  List of modules and a brief description of each  Brief functionality of each module  Interface relationship among modules  Dependencies between modules  Database tables identified with key elements  Overall architecture diagrams along with technology details Software Testing Concepts
20. Slide 20: 20 20 SDLC Phases- Design Low Level Design  Detailed functional logic of the module, in pseudo code  Database tables, with all elements, including their type and size  All interface details  All dependency issues  Error MSG listing  Complete input and output format of a module HLD and LLD phases put together called Design phase Software Testing Concepts
21. Slide 21: 21 21 SDLC Phases  Code Generation  design must be translated into a machine-readable form taking input as SRS.  Done by Team of developers.  Reviews after every 500 lines of code • Code Inspection • Code Walkthrough  Testing  New/patched build is tested by Test engineers for stability of the application.  Maintainence  Software is maintained due to changes ( unexpected values into the system) Software Testing Concepts
22. Slide 22: 22 22 Get Started with Testing !!!!!!!  What is testing?  We Test !! We Test !! Why?  Testing Defined  Is Product Successful  Product Success criteria  Testability  Test factors Software Testing Concepts
23. Slide 23: 23 23 What is Testing? process used to help identify the correctness, completeness and quality of developed computer software. Find out difference between actual and expected behavior. The process of exercising software to verify that it satisfies specified requirements of end user and to detect errors The process of revealing that an artifact fails to satisfy a set of requirements Software Testing Concepts
24. Slide 24: 24 24 What is Testing ( Cont.) ?  Establishing confidence that a system does what it is supposed to do  Confirming that a system performs its intended functions correctly  Does not guarantee bug free product  No substitute for good programming  Can’t prevent/debug bugs, only detect  Offer advise on product quality and risks. Software Testing Concepts
25. Slide 25: 25 25 We Test !! We Test !! Why Detect programming errors - programmers, like anyone else, can make mistakes. To catch bugs/defect/errors. To check program against specifications Cost of debugging is higher after release Client/end user should not find bugs Some bugs are easier to find in testing Challenge to release a bug-free product. Verifying Documentation. Software Testing Concepts
26. Slide 26: 26 26 We Test !! We Test !! Why?  To get adequate trust and confidence on the product.  To meet organizational goals  Like meeting requirements, satisfied customers, improved market share, Zero Defects etc  Since the software can perform 100000 correct operations per second, it has the same ability to perform 100000 wrong operations per second, if not tested properly.  Ensuring that system is ready for use  Understanding limits of performance.  Learning what a system is not able to do  Evaluating capabilities of system Software Testing Concepts
27. Slide 27: 27 27 Testing defined !!  Def-1  Process of establishing confidence that a program or system does what it is supposed to.  Def-2  Process of exercising or evaluating a system or system component by manual or automated means to verify that it satisfies specified requirement (IEEE 83a)  Def-3  Testing is a process of executing a program with the intent of finding errors (Myers)  Def-4  Testing is any activity aimed at evaluating an attribute or capability of a program or system and determining that it meets its required results. Software Testing Concepts
28. Slide 28: 28 28 Is Product successful ???  When Client/Customer perceives it as value-added to his business.  Timeliness of delivery of the product within budget and scope.  The business perceives that the system satisfactorily addresses the true business goals.  End user feels that look, feel, and navigation are easy.  Team is prepared to support and maintain the delivered product. Software Testing Concepts
29. Slide 29: 29 29 Product Success Criteria  Functionality  Usability  Likeability  Configurability  Maintainability  Interoperability Software Testing Concepts
30. Slide 30: 30 30 Testability  Operability  Controllability  Observability  Understandability  Suitability  Stability  Accessibility  Navigability  Editorial Continuity  Scalability  Context Sensitivity  Structural Continuity Software Testing Concepts
31. Slide 31: 31 31 Test Factors Functionality (exterior Engineering (interior Adaptability (future quality) quality) quality) Correctness Efficiency Flexibility Reliability Testability