Solved Past Paper of Software Quality Assurance 2018:
Q#1Differentiate between Software testing technique and strategy.
Software testing Techniques:
Software testing techniques are used to test an application to ensure it behaves and looks as expected. These encompass everything from front to back-end testing, including unit and system testing. This article is designed to highlight the myriad of testing techniques used by quality assurance professionals.
Testers are aware of the various types of Software Testing such as Functional Testing, Non-Functional Testing, Automation Testing, Agile Testing.
Software testing strategy:
A Software testing strategy is an outline that describes the testing approach of the software development cycle. The purpose of a test strategy is to provide a rational deduction from organizational, high-level objectives to actual test activities.
- Static Testing Strategy
- Structural Testing Strategy
Q#2 Draw cycle of Unit Testing?
Unit Testing Techniques:
- Black Box Testing - Using which the user interface, input and output are tested.
- White Box Testing - used to test each one of those functions’ behavior is tested.
- Gray Box Testing - Used to execute tests, risks and assessment methods.
Q#3 Four principles of Software Testing?
There are seven principles in software testing:
- Testing shows presence of defects
- Exhaustive testing is not possible
- Early testing
- Defect clustering
- Pesticide paradox
- Testing is context dependent
- Absence of errors fallacy
Q#4 What is FURPS Model?
FURPS is an acronym representing a model for classifying software quality attributes. FURPS model originally presented by Robert Grady.
FURPS stands for: Usability, Reliability, Performance and Supportability.
Functionality:
Which may include capabilities and security.
Usability:
Which may include human factors, user documentation, and training materials.
Reliability:
Which may include recoverability, predictability, accuracy, and mean time between failure.
Performance:
Which may include speed, efficiency, availability, accuracy, throughput, response time, recovery time.
Supportability:
Which may include testability, maintainability, compatibility, configurability, install ability.
Q#5 Name types of software reviews?
Software Review is systematic inspection of a software by one or more individuals who work together to find and resolve errors and defects in the software during the early stages of Software Development Life Cycle (SDLC). Software review is an essential part of Software Development Life Cycle (SDLC) that helps software engineers in validating the quality, functionality and other vital features and components of the software. It is a whole process that includes testing the software product and it makes sure that it meets the requirements stated by the client.
Types of Software Reviews:
There are mainly 3 types of software reviews:
- Software Peer Review
- Software Management Review
- Software Audit Review
Objectives of Software Review:
The objective of software review is:
- To improve the productivity of the development team.
- To make the testing process time and cost effective.
- To make the final software with fewer defects.
- To eliminate the inadequacies.
Long Questions
Q#2 Define White Box Testing, explain its one technique with relevant example.
White Box Testing:
White Box Testing is software testing technique in which internal structure, design and coding of software are tested to verify flow of input-output and to improve design, usability and security. In white box testing, code is visible to testers so it is also called Clear box testing, Open box testing, Transparent box testing, Code-based testing and Glass box testing.
White Box Testing Techniques:
- Statement Coverage - In this technique, the aim is to traverse all statement at least once. Hence, each line of code is tested. In case of a flowchart, every node must be traversed at least once. Since all lines of code are covered, helps in pointing out faulty code.
- Branch Coverage - This technique is running a series of tests to ensure that all branches are tested at least once.
- Path Coverage - This technique corresponds to testing all possible paths which means that each statement and branch is covered.
- Statement Testing = (Number of Statements Exercised / Total Number of Statements) x 100 %
- Branch Testing = (Number of decisions outcomes tested / Total Number of decision Outcomes) x 100 %
- Path Coverage = (Number paths exercised / Total Number of paths in the program) x 100 %
Q#4 Differentiate between validation and verification?
| # | Verification | Validation |
|---|---|---|
| 1 | The verifying process includes checking documents, design, code, and program | It is a dynamic mechanism of testing and validating the actual product |
| 2 | It does not involve executing the code | It always involves executing the code |
| 3 | Verification uses methods like reviews, walkthroughs, inspections, and desk- checking etc. | It uses methods like Black Box Testing, White Box Testing, and non-functional testing |
| 4 | Whether the software conforms to specification is checked | It checks whether the software meets the requirements and expectations of a customer |
|
|
|
|
| 5 | It finds bugs early in the development cycle | It can find bugs that the verification process can not catch |
| 6 | Target is application and software architecture, specification, complete design, high level, and database design etc. | Target is an actual product. |
| 7 | QA team does verification and make sure that the software is as per the requirement in the SRS document. | With the involvement of testing team validation is executed on software code. |
| 8 | It comes before Validation | It comes after Validation |
Software Quality Assurance Solved Past Paper 2019
Software Quality Assurance Solved Past Paper 2015