Scribd
Upload
4 views2 pages

exp8

The document outlines a laboratory experiment for a Software Testing course, focusing on preparing a test plan for a mobile application. It covers key concepts such as test approaches, test management, test case specifications, and parameters for a test summary report. The document emphasizes the importance of structured testing processes to ensure high-quality software delivery.

Uploaded by

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

exp8

The document outlines a laboratory experiment for a Software Testing course, focusing on preparing a test plan for a mobile application. It covers key concepts such as test approaches, test management, test case specifications, and parameters for a test summary report. The document emphasizes the importance of structured testing processes to ensure high-quality software delivery.

Uploaded by

nebuladreamerx
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

DEPARTMENT OF COMPUTER ENGINEERING

Subject: Software Testing Subject Code: 22518

Semester: 5th Course:

Laboratory No: Name of Subject Teacher: Supriya Angne

Name of Student: Satyam J. Bhambid Roll Id: 20203A0045

Experiment No: 08

Title of Experiment Prepare Test plan for an identified Mobile Application

Practical Related Questions

1. On which basis the Test Approach is decided for any application?

Answer: A test approach is the test strategy implementation of a project,


defines how testing would be carried out. Test approach has two techniques:
• Proactive - An approach in which the test design process is initiated as
early as possible in order to find and fix the defects before the build is
created.
• Reactive - An approach in which the testing is not started until after
design and coding are completed.

2. Define the Test Management


Answer:
• Test Management is a process of managing the testing activities in order to
ensure high quality and high-end testing of the software application.
• The method consists of organizing, controlling, ensuring traceability and
visibility of the testing process in order to deliver the high-quality software
application.

3. State the use of Test Case Specification. Enlist the Test Case Specification
Identifiers.
Page | 1
Answer:

Use of Test Case Specification:


It specifies the purpose of a specific test, identifies the required inputs and
expected results, provides step-by-step procedures for executing the test, and
outlines the pass/fail criteria for determining acceptance.

Test Case Specification Identifiers:

• Test Case Objectives: Purpose of the test


• Test Items: Items (e.g., requirement specifications, design specifications,
code, etc.) required to run a particular test case. This should be provided
in "Notes” or “Attachment” feature. It describes the features and
conditions required for testing.
• Input Specifications: Description of what is required (step-by-step) to
execute the test case (e.g., input files, values that must be entered into a
field, etc.). This should be provided in “Action” field.
• Output Specifications: Description of what the system should look like
after the test case is run. This should be provided in the “Expected
Results” field.
• Environmental Needs: Description of any special environmental needs.
This includes system architectures, Hardware & Software tools, records
or files, interfaces, etc

4. Enlist the parameters that should be considered while preparing Test


Summary Report.
Answer:
• Test summary report is a document which contains summary of test
activities and final test results. After the testing cycle it is very
• important that you communicate the test results and findings to the
project stakeholders.
• So that decisions can be made for the software release i.e. If further
testing is required and we need to delay the release.
• Test summary report will be different for different kind of testing.
• It should include relevant metrics and details regarding the software
testing process, such as test case adequacy, cost of finding defects, test
case effectiveness, test efficiency, rework & review efforts ratio, etc.
• In addition to test coverage and unresolved defects test summary reports
should also contain test strategy, test objectives and overall result of test
effort

Page | 2

You might also like