Software Quality Assurance
Download as PPTX, PDF1 like1,613 views
The document discusses software quality assurance. It defines SQA as using planned and systematic methods to evaluate software quality, standards, processes, and procedures. This ensures development follows standards and procedures through continuous monitoring, product evaluation, and audits. SQA activities include product evaluation and monitoring to ensure adherence to development plans, as well as product audits to thoroughly review products, processes, and documentation against established standards. Software reviews are used to uncover errors and defects during development in order to "purify" software requirements, design, code, and testing data before release.
Software Quality Assurance
- 1. SOFTWARE QUALITY ASSURANCE Presented By : Shashank Bajpai
- 2. Contents What is Quality ? What is Software Quality Assurance? Customer Wants Responsibilities of Testing Team Skills of Testing Team Tools for Software Quality Assurance Software testing team Test Manager Test Leader Testers How Software Quality Assurance Works? Standard Definition Types of Standards SQA Activities What S/W Review is used for? Team Thanks.
- 3. What is Quality ? Generally, the view about quality is related to luxury, class and taste. It is related to the quality of life. But in professional terms quality is related to the conformance to requirements.
- 4. What is Software Quality Assurance? Software Quality Assurance Plan (SQAP) consists of those procedures, techniques and tools used to ensure that a product meets the requirements specified in the software requirements specification.
- 5. Customer Wants Basically customer don’t buy product, they buy assurances that their expectations with the product would met. Customer is in absolute position to judge the quality. Only assurances(Quality) can also be sold.
- 6. Responsibilities of Testing Team Analyze requirements and prepare a query list. If requirements are incomplete, they need to ask meaningful questions that will yield more information and help perform testing effectively. Write and execute test cases to find system bugs like UI and usability issues, etc.
- 7. Responsibilities of Testing Team Check consistency across devices, browsers, and operating systems; Provide inputs on high-level test scenarios, challenges, risks, resources, test estimates, etc., during test planning meetings. In some cases, Teams can also cover test automation tasks.
- 8. Skills of Testing Team Deep understanding of software testing, its main concepts, and processes: the whole bug life cycle; different testing levels, methods, and types; test estimation techniques. Ability to work in an Agile environment. Critical thinking and analytical skills to examine bug reports and prioritize necessary tests, what information to include in the daily status reports, prioritize and estimate task execution.
- 9. Skills of Testing Team Good communication and teamwork skills to interact with project team members, clients, and stakeholders as well as work closely with the dev team – from reproducing the reported issue and emphasizing the fix for critical bugs to understanding how the bug has been fixed; Programming skills are always a plus including coding, basic SQL knowledge to extract data for tests, XML, general web development skills, and web services.
- 10. Tools for Software Quality Assurance Quality management tools (Micro Focus Quality Center, TestDirector, Test Manager, TestLink, SpiraTest, TestRail, HP-ALM (QC)) to organize and manage all phases of the software testing process including planning, running tests, and tracking defects, generating and storing test reports, and interlinking them with the release requirements; Defect tracking tools (BugZilla, Mantis, IBM Rational ClearQuest) to track the defects found in the application and generate bug reports to communicate them to the dev team; MS Excel or Test Studio to write large sets of test cases and later import them into TMTs;
- 11. Tools for Software Quality Assurance Project management software (Jira, Redmine, YouTrack, and Backlog); SQL clients to connect to the database; API testing tools (Postman, SoapUI, Katalon) for automated checks. They offer predefined snippets to automate API testing without the need to write code to test the API; IDEs for writing code (VSCode, Visual Studio, IntelliJ IDEA);
- 12. Software testing team Test manager: The role of test manager is optional. The test manager is hired when there are many testing groups. The number of testers and testing groups depends on the software testing workload. Test leader: Each test group is led by a test leader. The test leader performs the roles of test manager in absence of test manager. Testers: The testers group can comprise of entry level testers, senior testers, performance testers, automation testers and testers performing specific tests.
- 13. Test manager: Prepares test strategy Prepare the test budget Define test levels and test cycles Develop strategy for estimating test effort Develop strategy for test documentation, metrics and reporting
- 14. Test leader: Prepare the test plan at each test level based on test strategy Define the objectives, test items, approaches, risk, contingencies in testing process Assign roles and provide schedule to testers Identify the test specifications test activities for testers Gather metrics and track the testing progress
- 15. Testers: Gather the test requirements Review the project documents to understand the requirements and identify the errors Assist the test lead to prepare the test plan Create the test documents like traceability matrix, test data and test cases Set up and verify the test environment
- 16. How Software Quality Assurance Works? Using some Planned and systematic method that evaluate the quality of s/w products, standards, process & procedures. Ensure that development follow Standards and Procedures Done by Continuous Monitoring ▫ Product Evaluation ▫ Conducting Audits
- 17. Standard Definition Standard is a published specification that stablishes a common language and contains a technical specification and is designed to be used consistently as a rule, guideline, or a definition.
- 18. Type of Standards. Documentation Define the proper contents for planning and control Provide consistency throughout development life of project Design Define the proper form and content of the design product Methods for translating the software requirements specification into the actual software design Code Specify the programming language Also specify various constraints that should be put for usage of the language features (i.e use of data structures, patterns etc.)
- 19. SQA Activities Product Evaluation & Process Monitoring Ensures development processes and the control processes written in the management plan are carried out effectively Ensure that all the procedures and standards are correctly followed Products are continuously monitored for checking that it is following the standards and processes.
- 20. SQA Activities Product Evaluation Assures standards are being followed Ensures that the software application product is developed by conforming all the applicable standards as illustrated in the Management Plan Product Monitoring Ensures that the appropriate steps are carried out during the development process Comparing the actual steps carried out with those in the documented procedures Ensures that the Management Plan specifies the methods that should be used by the monitoring activity.
- 21. SQA Activities Product Audits That looks the entire product and all the processes in depth Done by comparing them with the established standards and procedures It’s an important activity to review the management plan, technical processes and assurance processes to provide the actual status of the software application product Main idea behind this is control procedures are properly followed and desired documentation is properly maintained SQA Product Is nothing but an audit report to display findings and recommendations to obey standards and procedures
- 22. What S/W Review is used for? “Filter” for software process Servers to uncover errors and defects that can then be removed “Purify” s/w including Requirements Design models Code Testing data Primary objective is to find errors during the process so that do not become defects after release of the s/w
- 23. Thank You