Past Paper of Software Quality Assurance 2019 Solved:
Q#1 Write 3 differences between White Box and Black Box testing?
# | Black Box Testing | White Box Testing |
---|---|---|
1 | Black Box Testing is the software testing method that is used to test the software without knowing the internal structure of code or program. | White Box Testing is the software testing method in which internal structure is being known to the tester who is going to test the software. |
2 | This type of testing is carried out by the testers. | Generally, This type of testing is carried out by software developers. |
3 | Implementation knowledge is not required to carry out Black Box Testing. | Implementation knowledge is required to carry out White Box Testing |
4 | Programming Knowledge is not required to carry out Black Box Testing. | Programming Knowledge is required to carry out White Box Testing. |
5 | Testing is applicable on higher levels of testing like System testing, Acceptance testing. | Testing is applicable on lower levels of testing like Unit testing, Integration testing. |
6 | Black Box Testing means functional test or external testing. | White Box Texting means structural test or internal testing. |
Q#2 Why do we use regression testing?
Regression Testing is a type of testing that is done to verify that a code change in the software does not impact the existing functionality of the product. This is to make sure the product works fine with new functionality, bug fixes, or any change in the existing feature.
Examples, bug regression, old fix regression testing, port testing, configuration testing, localization testing, smoke testing.
Q#3 What do you understand from the term PROCESS Quality?
Process-oriented quality indicates the quality aspects associated with the processes adopted for the production and transformation of the product. These aspects, therefore, include environmentally and/or socially sustainable processes and practices. Process-oriented quality attributes may or may not have an effect on product-oriented quality.
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 makes sure that the software is as per the requirement in the SRS document. | With the involvement of the testing, team validation is executed on software code. |
8 | It comes before Validation | It comes after Validation |
Long Questions
Q#1 Differentiate “Quality Control” And “Quality Assurance”?
Quality Assurance (QA) | Quality Control (QC) |
---|---|
It focuses on providing assurance that the quality requested will be achieved. | It focuses on fulfilling the quality requested. |
It is the technique of managing quality. | It is the technique to verify quality. |
It does not include the execution of the program. | It always includes the execution of the program. |
It is a managerial tool. | It is a corrective tool. |
It is process-oriented. | It is product-oriented. |
The aim of quality assurance is to prevent defects. | The aim of quality control is to identify and improve the defects. |
It is a preventive technique. | It is a corrective technique. |
It is a proactive measure. | It is a reactive measure. |
It is responsible for the full software development life cycle. | It is responsible for the software testing life cycle. |
Example: Verification | Example: Validation |
Q#3 What is meant by Testing? How many types of testing are there? Define Alpha and Beta Test.
Testing:
Testing is the process of executing a program with the aim of finding errors. To make our software perform well it should be error-free. If testing is done successfully it will remove all the errors from the software.
Types of Testing:
Functional Types:
- Unit Testing
- Integration Testing
- Regression Testing
- Smoke Testing
- Alpha Testing
- Beta Testing
- System Testing
- Stress Testing
- Performance Testing
Non-functional Testing types include:
- Performance Testing
- Load Testing
- Stress Testing
- Volume Testing
- Security Testing
- Alpha Testing:
Alpha Testing is a type of software testing performed to identify bugs before releasing the product to real users or to the public. Alpha Testing is one of the user acceptance testings.
This is a type of validation testing. It is a type of acceptance testing which is done before the product is released to customers. It is typically done by QA people.
Example:
When software testing is performed internally within the organization.
Beta Testing:
Beta Testing is performed by real users of the software application in a real environment. Beta testing is one of the types of User Acceptance Testing.
This version is released for a limited number of users for testing in a real-time environment
Example:
When software testing is performed for a limited number of people.
Software Quality Assurance Solved Past Paper 2014
Software Quality Assurance Solved Past Paper 2018