Your SlideShare is downloading. ×
0
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Software Testing Fundamentals
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Software Testing Fundamentals

38,431

Published on

13 Comments
26 Likes
Statistics
Notes
No Downloads
Views
Total Views
38,431
On Slideshare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
3,492
Comments
13
Likes
26
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Advantages of Usability Testing
    Usability test can be modified to cover many other types of testing such as functional testing, system integration testing, unit testing, smoke testing etc. (with keeping the main objective of usability testing in mind) in order to make it sure that testing is done in all the possible directions.
    Usability testing can be very economical if planned properly, yet highly effective and beneficial.
    If proper resources (experienced and creative testers) are used, usability test can help in fixing all the problems that user may face even before the system is finally released to the user. This may result in better performance and a standard system.
    Usability testing can help in uncovering potential bugs and potholes in the system which generally are not visible to developers and even escape the other type of testing.
    Usability testing is a very wide area of testing and it needs fairly high level of understanding of this field along with creative mind. People involved in the usability testing are required to possess skills like patience, ability to listen to the suggestions, openness to welcome any idea, and the most important of them all is that they should have good observation skills to spot and fix the problems on fly.
  • Testing where user plays a role/user is required: User Acceptance Testing: In this type of testing, the software is handed over to the user in order to find out if the software meets the user expectations and works as it is expected to. Alpha Testing: In this type of testing, the users are invited at the development center where they use the application and the developers note every particular input or action carried out by the user. Any type of abnormal behavior of the system is noted and rectified by the developers. Beta Testing: In this type of testing, the software is distributed as a beta version to the users and users test the application at their sites. As the users explore the software, in case if any exception/defect occurs that is reported to the developers.
  • Transcript

    • 1. By: Chankey Pathak chankey007@gmail.com http://www.technostall.com
    • 2. Agenda:- • Introduction • Importance of testing in SDLC • Testing life cycle • Test planning • Types of testing • Verification & Validation • Quality Assurance & Control • Bug reporting
    • 3. Software testing is a process used to identify the correctness, completeness and quality of developed computer software. It is the process of executing a program / application under positive and negative conditions by manual or automated means. It checks for the :-  Specification  Functionality  Performance Software Testing
    • 4. Software Testing is important as it may cause mission failure, impact on operational performance and reliability if not done properly. Effective software testing delivers quality software products satisfying user’s requirements, needs and expectations. Why Software Testing ?
    • 5. What …???? …is an ”ERROR”?? ….is a ”Bug”?? ….is Fault, Failure ??
    • 6. Bug, Fault & Failure Error : An error is a human action that produces the incorrect result that results in a fault. Bug : The presence of error at the time of execution of the software. Fault : State of software caused by an error. Failure : Deviation of the software from its expected result. It is an event. A person makes an Error That creates a fault in software That can cause a failure in operation
    • 7. Who is a Software Tester??.. Software Tester is the one who performs testing and find bugs, if they exist in the tested application.
    • 8. The Testing Team  Program Manager- • The planning and execution of the project to ensure the success of a project minimizing risk throughout the lifetime of the project. • Responsible for writing the product specification, managing the schedule and making the critical decisions and trade-offs.  QA Lead- • Coach and mentor other team members to help improve QA effectiveness • Work with other department representatives to collaborate on joint projects and initiatives • Implement industry best practices related to testing automation and to streamline the QA Department.
    • 9. Test AnalystLead- • Responsible for planning, developing and executing automated test systems, manual test plans and regressions test plans. • Identifying the Target Test Items to be evaluated by the test effort • Defining the appropriate tests required and any associated Test Data • Gathering and managing the Test Data • Evaluating the outcome of each test cycle Test Engineer- • Writing and executing test cases and Reporting defects • Test engineers are also responsible for determining the best way a test can be performed in order to achieve 100% test coverage of all components
    • 10. When to Start Testing in SDLC • Requirement • Analysis • Design • Coding • Testing • Implementation • Maintenance Testing starts from Requirement Phase
    • 11. Project Initiation System Study Summary Reports Analysis Regression Test Report Defects Execute Test Cases ( manual /automated ) Design Test Cases Test Plan Testing Life Cycle
    • 12. Test Plan A test plan is a systematic approach to testing a system i.e. software. The plan typically contains a detailed understanding of what the eventual testing workflow will be.
    • 13. Test Case A test case is a specific procedure of testing a particular requirement. It will include: • Identification of specific requirement tested • Test case success/failure criteria • Specific steps to execute test • Test Data
    • 14. Unit Testing 1.1. Test each module individually. 2. Follows a white box testing (Logic of the program) 3. Done by Developers
    • 15. Integration Testing After completing the unit testing and dependent modules development, programmers connect the modules with respect to HLD for Integration Testing through below approaches.
    • 16. System Testing After completing Unit and Integration testing through white box testing techniques development team release an .exe build (all integrated module) to perform black box testing. • Usability Testing • Functional Testing • Performance Testing • Security Testing
    • 17. Usability Testing During this test, testing team concentrates on the user friendliness of build interface. It consists of following sub tests. • User Interface Test: Ease of use (screens should be understandable to operate by End User) • Look & Feel :- attractive • Speed in interface :- Less number of task to complete task • Manual Support Test :- Context sensitiveness of user manual.
    • 18. Functional Testing• The process of checking the behavior of the application. • It is geared to functional requirements of an application. • To check the correctness of outputs. • Data validation and Integration i.e. inputs are correct or not.
    • 19. Performance Testing • LOAD TESTING – Also Known as Scalability Testing. During this test, test engineers execute application build under customer expected configuration and load to estimate performance. • STRESS TESTING – During this test, Test engineers estimates the peak load. To find out the maximum number of users for execution of out application user customer expected configuration to estimate peak load. PEAK LOAD > CUSTOMER LOAD (EXPECTED) • DATA VOLUME TESING -- Testing team conducts this test to find the maximum limit of data volume of your application.
    • 20. Security Testing Testing how well the system protects against unauthorized internal or external access, willful damage, etc, may require sophisticated testing techniques
    • 21. Smoke testing is non-exhaustive software testing, ascertaining that the most crucial functions of a program work, but not bothering with finer details. Smoke testing
    • 22. Alpha Testing 1. The application is tested by the users who doesn’t know about the application. 2. Done at developer’s site under controlled conditions 3. Under the supervision of the developers.
    • 23. Acceptance Testing A formal test conducted to determine whether or not a system satisfies its acceptance criteria and to enable the customer to determine whether or not to accept the system. It is the final test action before deploying the software. The goal of acceptance testing is to verify that the software is ready and can be used by the end user to perform the functions for which the software was built.
    • 24. Beta Testing 1. This Testing is done before the final release of the software to end-users. 2. Before the final release of the software is released to users for testing where there will be no controlled conditions and the user here is free enough to do what ever he wants to do on the system to find errors.
    • 25. Regression Testing Testing with the intent of determining if bug fixes have been successful and have not created any new problems. Also, this type of testing is done to ensure that no degradation of baseline functionality has occurred.
    • 26. Monkey Testing Testing the application randomly like hitting keys irregularly and try to breakdown the system there is no specific test cases and scenarios for monkey testing.
    • 27. Verification  Verification is the process confirming that -software meets its specification, done through inspections and walkthroughs Use – To identify defects in the product early in the life cycle
    • 28. Validation  Validation is the process confirming that it meets the user’s requirements. It is the actual testing. Verification : Is the Product Right Validation : Is it the Right Product
    • 29. Quality is defined as meeting the customer’s requirements and according to the standards The best measure of Quality is given by FURPS Functionality Usability Reliability Performance Scalability What is Quality ?
    • 30. Quality is the important factor affecting an organization’s long term performance.  Quality improves productivity and competitiveness in any organization. Why Quality ?
    • 31. Quality Assurance Quality Assurance is a planned and systematic set of activities necessary to provide adequate confidence that products and services will conform to specified requirements and meets user needs. •It is process oriented. •Defect prevention based. •Throughout the Life Cycle. •It’s a management process.
    • 32. Quality Control Quality control is the process by which product quality is compared with the applicable standards and the action taken when non conformance is detected. • It is product oriented • Defect detection based
    • 33. QA vs. QC• Quality Assurance makes sure that we are doing the right things, the right Way. • QA focuses on building in quality and hence preventing defects. • QA deals with process. • QA is for entire life cycle. • QA is preventive process. • Quality Control makes sure the results of what we’ve done are what we expected . • QC focuses on testing for quality and hence detecting defects. • QC deals with product. • QC is for testing part in SDLC. • QC is corrective process.
    • 34. Bug Life Cycle New Assigned Tester finds the bug and report it to Test Lead Test Lead confirms that it is a valid BugBug Resolved Re-open Verified Closed Deferred
    • 35. Cost Amount of Testing No.ofBugs Cost incurred Bugs ratio Stop Testing When to Stop Testing

    ×