Software Quality Assurance Procedures Quiz

1. What are the primary steps involved in the Software Quality Assurance (SQA) process?

• Analysis, Survey, Creation, Adjustment and Finalization.
• Programming, Deployment, Evaluation, Feedback and Update.
• Design, Development, Testing, Release and Review.
• Planning, Implementation, Assessment, Improvement and Documentation.

2. What is the purpose of an SQA plan?

• To specify the roles of developers and testers only.
• To define the QA process in detail, including procedures, tools, and techniques to ensure the product aligns with defined standards or the Software Requirements Specification (SRS).
• To create user manuals for the software system.
• To outline development tasks without focusing on quality metrics.

3. What areas are typically listed in an SQA plan?

• Project scheduling and resource allocation, team collaboration metrics, user feedback mechanisms, code repository management.
• Software configuration management, problem reporting and corrective action, tools and methodologies, code control, records for collection, maintenance, and retention, testing methodology.
• Customer satisfaction assessment, marketing strategies, financial forecasting, team budget allocation.
• User interface design principles, content management systems, deployment strategies, web performance optimization.

4. What is manual testing in software testing?

• Manual testing involves manual inspection and testing of the software by a human tester.
• Manual testing skips the execution of test cases and focuses on documentation.
• Manual testing is done using automated tools to simulate user actions.
• Manual testing requires only automated scripts to validate software behavior.

5. What is automated testing in software testing?

• Automated testing is focused only on visual interface testing.
• Automated testing solely relies on user feedback for quality checks.
• Automated testing involves using software tools to automate the testing process.
• Automated testing uses manual techniques for error detection.

6. What is functional testing in software testing?

• Functional testing evaluates the performance of software under stress conditions.
• Functional testing involves reviewing the source code for compliance with standards.
• Functional testing measures the security aspects of the software system.
• Functional testing tests the functional requirements of the software to ensure they are met.

7. What is non-functional testing in software testing?

• Non-functional testing measures customer satisfaction and feedback.
• Non-functional testing evaluates performance, security, and usability.
• Non-functional testing checks code structure and syntax errors.
• Non-functional testing verifies software against user requirements.

8. What is unit testing in software testing?

• Unit testing focuses solely on the user interface of the software application.
• Unit testing tests individual units or components of the software to ensure they are functioning as intended.
• Unit testing tests the entire software application to check overall performance.
• Unit testing involves testing network security and data integrity of the software.

9. What is integration testing in software testing?

• Integration testing primarily checks each individual component before integration.
• Integration testing is the final step before releasing the software to customers.
• Integration testing is mainly focused on the aesthetic design of the software interface.
• Integration testing tests the integration of different components of the software to ensure they work together as a system.

10. What is system testing in software testing?

• System testing evaluates user interface design for aesthetic appeal and usability.
• System testing tests the complete software system to ensure it meets the specified requirements.
• System testing conducts performance tests specifically for database queries and loads.
• System testing verifies individual code segments function correctly in isolation.

11. What is acceptance testing in software testing?

• Acceptance testing focuses on improving the code efficiency of the software.
• Acceptance testing evaluates the software development team’s performance.
• Acceptance testing checks for software compatibility with multiple devices.
• Acceptance testing tests the software to ensure it meets the customer’s or end-user’s expectations.

12. What is regression testing in software testing?

• Regression testing ensures changes haven`t introduced new defects.
• Regression testing verifies the software`s documentation.
• Regression testing checks compliance with coding standards.
• Regression testing focuses on performance and usability tests.

13. What are the two main categories of software testing techniques?

• Automated Testing Techniques and Manual Testing Techniques
• Integration Testing Techniques and Unit Testing Techniques
• Performance Testing Techniques and Load Testing Techniques
• Static Testing Techniques and Dynamic Testing Techniques

14. What is static testing in software testing?

• Static testing involves running the software to find bugs.
• Static testing techniques find defects without executing code.
• Static testing uses automated tools to execute the software.
• Static testing requires user acceptance for validating functionalities.

15. What is dynamic testing in software testing?

• Dynamic testing techniques are used to test the dynamic behavior of the application under test by executing the code base.
• Dynamic testing measures application performance under theoretical conditions.
• Dynamic testing involves reviewing code without executing it.
• Dynamic testing consists of creating documentation without running tests.

16. What are the seven steps of the software testing process?

• Test planning, test monitoring & control, test analysis, test design, test implementation, test execution, test completion.
• Test planning, requirement gathering, code review, deployment, user acceptance, system testing, test closure.
• Test initiation, user feedback, performance analysis, bug fixing, testing tools, release planning, support.
• Planning, coding, debugging, documentation, deployment, integration, maintenance.

17. What is test planning in the software testing process?

• In test planning, we write the test plan, which includes the activities that will be carried out throughout our test process.
• Test planning involves only writing code without any oversight.
• Test planning is about executing tests without prior organization.
• Test planning focuses solely on documenting bugs after testing.

18. What is test monitoring & control in the software testing process?

• In test monitoring, we only report defects found during testing.
• In test monitoring, we compare our progress and what is stated in the test plan. If there is a deviation, we perform control activities to resolve it.
• In test monitoring, we develop new test cases and scenarios.
• In test monitoring, we do not need to follow the test plan at all.

19. What is test analysis in the software testing process?

• In test analysis, we create marketing plans to promote the software.
• In test analysis, we review the work products (requirements-user stories-design) to define our test scenarios.
• In test analysis, we conduct user training for the new software application.
• In test analysis, we develop the software`s code and features.

20. What is test design in the software testing process?

• In test design, we implement the coding standards for the application.
• In test design, we conduct performance measurement of the software.
• In test design, we turn the test scenarios into test cases.
• In test design, we develop user requirements and specifications.

21. What is test implementation in the software testing process?

• In test implementation, we define the requirements and specifications of the software.
• In test implementation, we conduct user training sessions and gather user feedback.
• In test implementation, we set up the test environment and prepare to execute our tests.
• In test implementation, we perform maintenance on the software after its release.

22. What is test execution in the software testing process?

• In test execution, we finalize project requirements and establish deadlines.
• In test execution, we create new tests and design the testing environment.
• In test execution, we analyze defects and conduct user training sessions.
• In test execution, we execute our test scenarios or test cases and report defects found.

23. What is test completion in the software testing process?

• In test completion, we only summarize the testing activities without fixing defects.
• In test completion, we prepare the software for release without any further testing.
• In test completion, we ensure all defects are fixed and write a test summary report.
• In test completion, we create a list of all bugs found during testing for future reference.

24. What are the four general steps of the QA process?

• Identify, Test, Approve, Release
• Analyze, Develop, Review, Implement
• Research, Design, Execute, Evaluate
• Plan, Do, Check, Act

25. What is the primary objective of formal technical reviews?

• To finalize the software design before coding.
• To ensure all software features are developed.
• To find errors during the process so they do not become defects after release of the software.
• To reduce development costs at any expense.

26. Who identifies, documents, and verifies corrections made to the software?

• The Marketing team
• The Sales team
• The Development team
• The SQA group

27. What are appraisal costs in SQA?

• Appraisal costs relate solely to software deployment stages.
• Appraisal costs include inter-process inspection, maintenance, quality planning, and testing.
• Appraisal costs do not consider alignment with quality standards.
• Appraisal costs include only testing and documentation.

28. What are prevention costs in SQA?

• Prevention costs include quality planning, formal technical reviews, test equipment, equipment calibration and maintenance.
• Prevention costs comprise testing methodology and problem reporting.
• Prevention costs involve defect tracking, customer feedback, and inspections.
• Prevention costs consist of warranty claims and software repair.

29. What are failure costs in SQA?

• Failure costs only relate to external testing charges.
• Failure costs include rework, repair, and failure mode analysis.
• Failure costs only represent employee training expenses.
• Failure costs involve only documentation and reporting.

30. What are external failure costs in SQA?

• External failure costs include testing, help line support, warranty work, and complaint resolution.
• Internal failure costs involve inspections and rework activities.
• Prevention costs are related to initial quality planning and development.
• Evaluation costs cover customer feedback and product updates.