Scribd
Upload
14 views7 pages

Comprehensive Software Testing Question Bank

STE 22518 final question bank

Uploaded by

arqamqazi549
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
14 views7 pages

Comprehensive Software Testing Question Bank

STE 22518 final question bank

Uploaded by

arqamqazi549
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

STE QUESTION BANK 22518

Chapter 1: Basics of Software Testing and Testing Method (14


Marks)
2 Marks question
1. Define static and dynamic testing. (W-19)
2. Enlist objectives of software testing. (W-19) (W-23) (S-24) OR
Give the objectives of software testing. (W-22)
3. Define Bug, Error, Fault and Failure. (W-19) (S-22) (W-23)
OR
Define Error, Fault, Defect Bug. (W-22)
Define following terms i) Defect ii) Bug (S-23)
Define the terms error and defect in relation with software testing. (S-24)
4. Define verification and validation with respect to software testing. (S-22)
5. Enlist any four skills for software tester. (S-22) (S-24)
6. Compare verification and validation (any two points). (W-22) (W-23)
7. Write two differences between quality assurance and quality control. (S-
23)
8. Write steps to prepare test cases. (S-23)
4 Marks question
1. Describe Boundry value analysis with suitable example. (W-19) (W-23)
2. Describe the use of decision table in black box testing with the help of
suitable example. (W-19)
3. State the Entry and Exit criterias for the software testing. (W-22) (W-23)
4. Differentiate between white box testing and black box testing (any four
points). (W-22) (S-24)
5. Describe any four skills of software tester. (S-23)
6. List types of white box testing. Describe any two types of white box
testing with neat diagram. (S-23)
7. Describe Code Complexity testing. (S-22)
8. Write any four differences between quality assurance and quality control.
(S-22) (S-24)
9. Explain test case specification. (S-22)
[Link] the test cases for Notepad application. (any eight test case) (W-22)
6 Marks question
1. Design test cases for railway reservation system. (W-19)
2. Design test cases for hostel admission form of your institute. (W-19)
3. Design test cases for Online Mobile Recharge (Data filed are mobile
number, state, email-id, recharge amount.) (S-22)
4. Design test cases for Web pages testing of any Web site (take a suitable
example). (W-22)
5. Write program for calculating even numbers from 1 to 20 And design test
cases for the same. (W-22)
6. Design test cases for hostel admission form. (S-23)
7. Design test cases for online railway reservation applications. (S-23)
8. Describe V-model with labelled diagram. (W-23)
9. Prepare six test cases for marketing site [Link]. (W-23)
[Link] important six test cases for the ‘Login Form’ of the Facebook
website. (W-23)
[Link] and write six test cases for Library Management System of
college. (S-24)

Chapter 2: Types and Levels of Testing (18 Marks)


2 Marks question
1. State any two example of integration testing. (W-19)
2. State the process of performance testing. (S-22)
3. List the levels of testing. (W-22)
4. Enlist any two advantages of acceptance testing. (S-23)
5. Define Driver and stub. (W-23)
6. What is GUI testing ? Give one example. (W-23)
7. Compare Alpha testing and Beta testing. (Any two differences). (S-24)

4 Marks question
1. Differentiate between drivers and stub (any four points) (W-19)
2. Differentiate between alpha and beta testing (any four points) (W-19) (W-
23)
3. State the testing approaches that are considered during client-server
testing. (W-19)
4. Differentiate between Smoke Testing and Sanity Testing. (any four
points). (S-22)
5. Describe Unit Testing. (S-22)
6. Explain following concepts related to security testing – i) Authorization.
ii) Access Control. (S-22)
7. State and describe top-down approach of integration testing with diagram.
(W-22)
8. Describe the types of integration testing with neat diagram. (S-23)
9. Illustrate process of bi-directional integration testing. State its two
advantages & disadvantages. (W-23)
[Link] graphical user interface (GUI) testing and its important traits.
(W-22)
[Link] GUI testing with example. (S-24)
[Link] the process of performance testing. (S-24)
[Link] load testing and stress testing with suitable example. (W-22)
[Link] the factors considered to decide test approach. (S-23)
[Link] the testing approaches that are considered during web application
testing. (S-23)
[Link] the regression testing. State entry and exit criteria for regression
testing. (S-23)
[Link] the Regression testing. State when the Regression testing shall be
done. (W-23)
[Link] acceptance testing with its advantages. (S-24)
6 Marks question
1. With respect to GUI testing write the test cases for Amazon login form.
(W-19)
2. With respect to client-server testing design test cases for Online Payment
Transfer at banking system. (S-22)
3. With respect to GUI testing, write test cases for Flipkart login form. (S-
22)
4. Design test cases for simple calculator application. (Black box testing.)
(Any six points.) (W-22)
5. Write test cases for facebook login form with respect to graphical user
interlac (GUI) testing (S-23)
6. Describe with one example each : (i) Load testing (ii) Stress testing (W-
23)
7. Explain client-server testing with suitable diagram. (W-23) (S-24)
8. Explain the need of stubs and drivers with diagram and its importance in
software testing. (S-24)
Chapter 3: Test Management (14 Marks)

2 Marks question
1. Define a test plan. (S-24)
2. Define test plan with two advantages. (S-23)
3. Enlist any two activities involved in test planning. (W-19)
4. Enlist different types of test deliverables. (S-22)
5. State any four needs to prepare a test plan. (W-22)

4 Marks question
1. State the contents of ‘Test Summary Reports’ used in test reporting. (W-
19) (W-22) (S-24)
2. Describe the process of preparing summary report in test planning. (W-
19)
3. Explain test reporting with executing test cases and preparing test
summary report. (S-22)
4. Describe standards included in Test Management. (W-19)
5. Explain test management with Test Infrastructure Management and Test
People Management. (S-22)
6. Describe test management with test people management. (S-23)
7. Explain people management in test planning. (S-24)
8. Describe test infrastructure management (W-19)
9. Explain test infrastructure management with its component. (W-22) (S-
23) (S-24)
[Link] different types of external standards. (S-22)
[Link] test deliverables in details. (W-22)
[Link] the need of test deliverables & test plan for test planning. (S-24)
[Link] is test plan ? What is its need ? List test planning activities. (W-23)
[Link] test plan for Notepad application. (Windows based) (W-23)
6 Marks question
1. Design a test plan along with the test cases for edit function in notepad.
(W-19)
2. Prepare a test plan along with test cases for creating a saving account at
bank. (Test cases should be atleast six). (S-22)
3. Prepare test plan for ‘Cam Scanner’ which is installed on mobile. (W-22)
4. Prepare a test plan along with the test cases for the MS Excel option
“Save AS”. (S-23)
5. Explain in detail, how to prepare a test plan with suitable example. (S-24)
Chapter 4: Defect Management (12 Marks)

2 Marks question
1. Define Defect (W-19)
2. Give the defect classification and its meaning. (W-22)
3. State any four attributes of defect. (S-23)
4. Write any two root causes of defect. (W-23)
5. State the classification of defects. (S-24)

4 Marks question
1. Enlist different techniques for finding defects and describe any one
technique with an example. (W-19)
2. State any four defect reporting guidelines. (S-22)
3. Draw defect prevention process cycle. State working of each phase. (S-
22)
4. Describe defect management process with neat diagram. (W-23) (S-23)
(S-24)
5. Enlist any four attributes of defect. Describe them with suitable example.
(W-23)
6. Prepare defect report after executing test cases for any login form. (W-22)
7. Prepare defect report for login field of email application. (W-23)
6 Marks question
1. Draw a diagram for defect life cycle and write example for defect
template. (W-19)
2. Design any four test cases for withdraw an amount from ATM and
prepare defeat report of it. (S-22)
3. Prepare defect report after executing test cases for withdrawn of amount
from ATM machine. (W-22)
4. Design test cases for online shopping website flipkart and prepare defect
report of it. (S-23)
5. Describe defect life cycle with neat diagram. (W-23)
6. Draw a diagram for defect life cycle and write example for defect
template. (S-24)
Chapter 5: Testing Tools and Measurements (12 Marks)
2 Marks question
1. State any four advantages of using tools. (W-19)
2. State the need of automated testing tools. (W-22) (S-24)
3. State any two difference between manual and automated testing. (S-23)
4. Enlist any four software testing tools. (W-23) (S-22)

4 Marks question
1. State any eight limitations of manual testing. (W-19) (S-22)
OR
State the limitations of manual testing. (W-22) (W-23) (S-23) (S-24)
2. Enlist factors considered for selecting a testing tool for test automation.
(W-19) (W-22)
OR
Describe any four factors for selecting a testing tools. (S-22) (W-23)
3. Describe the criterias to select testing tools. (S-23)
4. Describe object oriented metrics in testing. (W-19)
5. Describe need for Automated Testing tools. (S-22)
OR
State & explain any four benefits of automation in testing. (W-23)
6. State the advantages and disadvantages of using tools. (W-22)
7. Give any four differences between manual and automated testing. (Any 4
points) (S-24)
8. Differentiate between static and dynamic testing tools. (any four points)
(S-23) (S-24)
6 Marks question
1. Elaborate the term metrics and measurement and write the need of
software measurement. (W-19)
2. Elaborate the concept of Software Metrics? Describe Base Metrics and
calculated matrics with suitable example. (S-22)
3. Define metrics and measurements. Describe three types of metrics. (S-23)
4. Design test cases for MS Word application using an Automation tool.
(W-22)
5. How to select a testing tool? Explain in detail. (S-24)

Common questions

Powered by AI

White box testing involves evaluating software based on the internal code structure, requiring knowledge of coding and often used by developers. Its focus is on code paths, decision branches, and code complexity. Black box testing, in contrast, tests software functionality without examining internal structures, focusing on input/output and user experience. It doesn't require coding knowledge, making it more suitable for end-users or testers who ensure user requirements are met. These approaches differ in the level of detail, user perspective, understanding of internal code, and the specific focus of testing practices .

Static testing involves reviewing the software's documentation and code without executing the program, aiming to identify errors or defects early. Dynamic testing requires executing the software to verify its functionality, performance, and output against expected results. This approach often uncovers runtime errors that static testing may miss .

A test plan is crucial as it outlines the testing strategy, objectives, resources, schedules, and scope, serving as a blueprint for the testing process. It ensures systematic and thorough testing by detailing the approach, risk analysis, test objectives, criteria for pass/fail, test deliverables, and responsibilities. The test plan enhances communication among stakeholders, aligns testing with project objectives, and aids in resource and time management .

Drivers and stubs are used to simulate components during integration testing. A driver calls a module under test, serving as a control mechanism for integration, whereas a stub simulates a module that is called by the module under test. These tools facilitate testing by allowing isolated testing of components and help in scenarios where certain modules are not yet developed or integrated, enabling early testing and identification of defects .

The defect management process involves identifying, documenting, analyzing, prioritizing, and tracking defects until resolution. This process is significant in the software development lifecycle because it improves quality control, facilitates communication among developers and testers, and ensures that defects are addressed systematically and efficiently. It aids in risk management and helps maintain project timelines and costs by resolving issues proactively before they escalate .

Top-down integration testing begins with the highest-level components and integrates downwards, often using stubs to simulate lower modules. This approach ensures testing of the high-level logic early but may delay testing of lower-level functionality. Bottom-up testing starts with the lowest-level components, gradually integrating upwards using drivers. It allows for effective testing of detailed functionalities first but might delay the testing of high-level architecture. Both methods assure comprehensive integration testing but differ in focus and execution order .

The objectives of software testing, which include verifying that the software meets specified requirements, ensuring defects are identified and addressed, gauging software reliability, and enhancing software quality, align with the development lifecycle by ensuring that each phase's deliverables meet quality standards. This alignment fosters user satisfaction, reduces costly post-release defects, and aids in efficient project management by mitigating risks and facilitating maintenance .

Boundary value analysis enhances black box testing by targeting the edges of input ranges where errors frequently occur, thus improving the discovery of off-by-one errors and other edge case anomalies. Decision table testing provides a structured approach to testing complex logic by mapping different input combinations to expected outcomes, ensuring comprehensive coverage of business rules and reducing ambiguity. Both techniques contribute to thorough testing by identifying hidden defects that may not be apparent in normal operations .

Selecting an automated testing tool requires considering factors such as the tool's compatibility with the technology stack, ease of use, scalability, community support, integration capabilities, and cost. These considerations are crucial because they affect the tool's effectiveness, efficiency, and return on investment. A well-chosen tool enhances testing reliability, reduces manual effort, optimizes resources, and ensures successful adoption by aligning with the team's technical and operational needs .

Verification and validation both aim to ensure software quality, but they differ in approach and focus. Verification is a static method of checking whether a system meets specifications and is often conducted through reviews and inspections. Validation, a dynamic method, checks whether the system meets the user's actual needs and must be executed through actual testing. Both processes are integral to quality assurance, ensuring the software meets both specified and real-world requirements .

You might also like