STQA University Questions

Dec’17, May’17, Dec’16, May’16

● Not Repeated
● Repeated Once
● Repeated Twice

1. Introduction to Software Testing

5 marks
1. Differentiate between Effective and Exhaustive Software Testing.
2. How does Testing help in producing Quality Software.

10 marks
1. What is Software Testing? Describe Software Testing model with neat diagram.

2. Software Testing Terminology and Methodology

5 marks
1. With example explain Failure, Defect and Error.
2. Explain STLC.

10 marks
1. Bug classification based on SDLC.
2. What is bug? Explain Life Cycle of bug and different stages of bug.

3. Verification and Validation

5 marks
1. Differentiate between Verification and Validation.

10 marks
1. What is Verification and Validation? What is its need?
2. Discuss the benefits of Verification and Validation in a Project.

4. Dynamic Testing: Black Box Testing Techniques

5 marks
1. What are the types of errors detected by Black Box Testing?

10 marks
 1.

2.

3.
4. Explain with example class Testing.

5. Dynamic Testing: White Box Testing Techniques

5 marks
1. Differentiate between White Box and Black Box Testing.

10 marks

1.
2.
3. Explain Mutation Testing with the help of an example.
 6. Static Testing
10 marks
1. Explain Static Data Flow Testing.
2. What is Static Testing? Explain the types of Static Testing.

7. Validation Activities
5 marks
1. Acceptance Testing.
2. Differentiate between Top-Down and Bottom-Up Testing.

10 marks
1. Explain different types of incremental Integration Testing methods.
2. Explain entry and exit criteria for Alpha and Beta Testing. How Alpha Testing differs from
Beta Testing.
3. Why do we need Integration Testing? Explain various approaches in Integration Testing.

8. Regression Testing
10 marks
1. Explain the Regression Testing types.
2. Regression Testing.

9. Test Management
5 marks
1. Explain Structure of Testing Group.

10 marks
1. Explain Test Design Preparedness metrics.

10. Software Metrics

5 marks
1. Explain different Size metrics.

10 marks
1. Explain the need of Software Metrics.
2. What is the need for Software measurement? Discuss the various types of Software
Metrics.
 11. Testing Metrics for Monitoring and Controlling the Testing Process
5 marks
1. Function point metric for Software Testing.

10 marks
1. Explain the process of Testing Point Analysis.
2. What is Test Point Analysis.

3.

12. Efficient Test Suite Management

5 marks
1. What is Test Suite? Why it grows?
2. Test Suite Minimization problem.

10 marks

1.
 2.

13. Automation and Testing Tools

5 marks
1. Elaborate on SQA models in brief.

10 marks
1. Explain the guidelines for Automated Testing.

14. Testing Object Oriented Software

5 marks
1. Issues in Object Oriented Testing.

10 marks
1. Object Oriented Testing.

15. Testing Web-based Systems

10 marks
1. What are the challenges in Testing Web-based Softwares.
2. Explain Security Testing in web based applications.

16. Software Quality Management

5 marks
1. Explain Software Quality Metrics.
10 marks
1. Software Quality Management.
2. Explain 9126 Quality Characteristics.

Unknown
5 marks
1. Challenges in Testing Data Warehouse.

Importance of Data Warehouse testing

● Organizations with already well defined IT practices are at an innovative stage to

create the next level of technology transformation, by constructing their own data
warehouse to store and monitor real-time data.
● They have realized the need to test this data to ensure data completeness and
data integrity. They have also realized the fact that comprehensive testing of data
at every point throughout the ETL process is important and inevitable, as more of
this data is being collected and used for strategic decision-making that affects
their business forecasts.
● But, certain current strategies being followed are time-consuming,
resource-intensive, and inefficient. Thus, a well-planned, well defined and
effective ETL testing scope guarantees smooth conversion of the project to the
final production phase. Now, let us see some of the issues that are common with
ETL and Data Warehouse testing.

ETL Testing

● An ETL tool extracts the data from all these heterogeneous data sources,
transforms the data (like applying calculations, joining fields, keys, removing
incorrect data fields, etc.), and loads it into a Data Warehouse.
● ETL stands for Extract-Transform-Load and is a typical process of loading data
from a source system to the actual data warehouse and other data integration
projects.
● It is important to know that independent verification and validation of data is
gaining huge market potential.

Some of the important ETL Testing Challenges are:

● Loss of data might be there during the ETL process

● Incorrect, incomplete or duplicate data.
● DW system contains historical data, so the data volume is too large and
extremely complex to perform ETL testing in the target system.
 ● ETL testers are normally not provided with access to see job schedules in the
ETL tool. They hardly have access to BI Reporting tools to see the final layout of
reports and data inside the reports.
● Tough to generate and build test cases, as data volume is too high and complex.
● ETL testers normally don’t have an idea of end-user report requirements and
business flow of the information.
● ETL testing involves various complex SQL concepts for data validation in the
target system.
● Sometimes the testers are not provided with the source-to-target mapping
information.
● Unstable testing environment delay the development and testing of a process.

10 marks
1. Explain the McCall’s quality factors.

A quality factor represents a behavioural characteristic of a system. Following are the list
of quality factors:

1.Correctness:

● A software system is expected to meets the explicitly specified functional

requirements and the implicitly expected non-functional requirements.
● If a software system satisfies all the functional requirements, the system is said to
be correct.

2.Reliability
 ● Customers may still consider an incorrect system to be reliable if the failure rate
is very small and it does not adversely affect their mission objectives.
● Reliability is a customer perception, and an incorrect software can still be
considered to be reliable.

3.Efficiency:

● Efficiency concerns to what extent a software system utilizes resources, such as

computing power, memory, disk space, communication bandwidth, and energy.
● A software system must utilize as little resources as possible to perform its
functionalities.

4.Integrity:

● A system’s integrity refers to its ability to withstand attacks to its security.

● In other words, integrity refers to the extent to which access to software or data
by unauthorized persons or programs can be controlled.

5.Usability:

● A software is considered to be usable if human users find it easy to use.

● Without a good user interface a software system may fizzle out even if it
possesses many desired qualities.

6.Maintainability:

● Maintenance refers to the upkeep of products in response to deterioration of their

components due to continuous use of the products.
● Maintenance refers to how easily and inexpensively the maintenance tasks can
be performed.
● For software products, there are three categories of maintenance activities :
corrective, adaptive and perfective maintenance.

7.Testability:

● Testability means the ability to verify requirements. At every stage of software

development, it is necessary to consider the testability aspect of a product.
● To make a product testable, designers may have to instrument a design with
functionalities not available to the customer.

8.Flexibility:

● Flexibility is reflected in the cost of modifying an operational system.

 ● In order to measure the flexibility of a system, one has to find an answer to the
question: How easily can one add a new feature to a system.

9.Portability

● Portability of a software system refers to how easily it can be adapted to run in a

different execution environment.
● Portability gives customers an option to easily move from one execution
environment to another to best utilize emerging technologies in furthering their
business.

10.Reusability

● Reusability means if a significant portion of one product can be reused, maybe

with minor modifications, in another product.
● Reusability saves the cost and time to develop and test the component being
reused.

11.Interoperability :

● Interoperability means whether or not the output of one system is acceptable as

input to another system, it is likely that the two systems run on different
computers interconnected by a network.
● An example of interoperability is the ability to roam from one cellular phone
network in one country to another cellular network in another country.

McCall’s Quality Criteria :

A quality criteria is an attribute of a quality factor that is related to software development.

For example, modularity is an attribute of the architecture of a software system.

List of McCall’s Quality Criteria :

1.Access Audit : Ease with which the software and data can be checked for compliance
with standards.

2.Access Control : Provisions for control and protection of the software

3.Accuracy : Precisions of computations and output.

4.Completeness: Degree to which full implementation of required functionalities have

been achieved.

5.Communicativeness : Ease with which the inputs and outputs can be assimilated.

6.Conciseness : Compactness of the source code, in terms of lines of code.

 7.Consistency : Use of uniform design and implementation techniques.

8.Data commonality : Use of standard data representation.

9.Error tolerance : Degree to which continuity of operation is ensured under adverse

conditions.

10.Execution efficiency : Run time efficiency of the software.

11.Expandability : Degree to which storage requirements or software functions can be

expanded.

12.Hardware independence : Degree to which a software is dependent on the underlying

hardware.

13.Modularity : Provision of highly independent modules.

14.Operability : Ease of operation of the software.

15.Simplicity : Ease with which the software can be understood.

16.Software efficiency : Run time storage requirements of the software.

17.Traceability : Ability to link software components to requirements.

18.Training : Ease with which new users can use the system.

2. Design Test Case to find maximum of 4 numbers.

Steps Description Input Data Expected Result Actual Result

1 Enter 4 numbers 0 to 9 (For eg: 10,15,2,8) 10,15,2,8

Inputs Accepted

2 Enter numbers and 0 to 9 ; A to Z ; a Invalid inputs Invalid

alphabets to z

3 Enter numbers and 0 to 9 ; Invalid inputs Invalid

special characters ~,!,@,#,$,%,^,&,*
,(,),_,-
4 Enter numbers and 0 to 9 and space Invalid inputs Invalid
spaces

5.1 Comparing 1st pair of (10>15)?10:15 15 15

accepted inputs

5.2 Comparing 2nd pair of (15>2)?15:2 15 15

accepted inputs

5.3 Comparing 3rd pair of (2>8)?2:8 8 8

accepted inputs

6.1 Comparing obtained 1st (15=>15)?15:15 15 15

output pairs

6.2 Comparing obtained (15=>8)?15:8 15 15

2nd output pairs