0% found this document useful (0 votes)
361 views

Software Practical No 8

The document provides a test plan for a Food Delivery Application. The test plan aims to evaluate the application's functionality and usability through testing. Key items to be tested include creating an account, entering customer details, order preparation, and delivery. Features like account creation, content display, and closing the application will be tested along with writing test cases and reports. Approval is needed from the team lead and test engineers.

Uploaded by

ayush
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
361 views

Software Practical No 8

The document provides a test plan for a Food Delivery Application. The test plan aims to evaluate the application's functionality and usability through testing. Key items to be tested include creating an account, entering customer details, order preparation, and delivery. Features like account creation, content display, and closing the application will be tested along with writing test cases and reports. Approval is needed from the team lead and test engineers.

Uploaded by

ayush
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Name: Ayush Maroti Wadje Roll no:76

Sub: STE

Practical No.08
Prepare Test Plan for an identified Mobile Application.

Test Plan for Mobile Messenger

1. Introduction :

The purpose of this document is to create an application test plan for


Mobile messenger. The presented study test plan evaluates the approaches
to testing this product. The purpose of testing this program is to check the
correct operation of its functionality, ease of use.
2. Scope:
The scope of work is defined at the beginning of the testing process.
A project team should clearly understand what features and functions
there are to be tested and which ones are out of scope. To determine
the scope of testing, the project specification, budget, and customer’s
requirements should be taken into account
3.Test Items:
• Working with the program (opening, closing, etc.)
• Create a message
• Sending a message
• Receiving message
5. Features to be tested:
• Running a Mobile Messenger
• Create a message
• Adding contacts
• Send message
• Delete Message
• Forward message
• Closing the Mobile Messenger
6. Features not to be tested:

• Working with Help


• Security testing
• Interoperability testing

7. Staffing and training needs:

• knowledge and practical application of the IEEE-829 standard;


• knowledge and ability to apply in practice the basic techniques of test
design
• knowledge of various types of testing including functional and
nonfunctional.

8.Test tasks:

• Writing a test plan


• Writing test cases
• Development of criteria for the success of testing
• Conducting the testing and evaluation of the results
• Creating test reports

9. Testing tools:
• Computer: having Windows support
• Test tool: develop a test tool which can auto generate the test result to the
predefined form and automated test execution

10. Approvals:

• Team Lead
• Test engineer 1
• Test engineer 2 • Test engineer 3
• Test engineer 4
Test Plan for Food Delivery Application

3. Introduction :

The purpose of this document is to create an application test plan for Food
Delivery Application. The presented study test plan evaluates the
approaches to testing this product. The purpose of testing this program is
to check the correct operation of its functionality, ease of use

4. Scope:

All the features of the Food Delivery Application are need to be tested

3.Test Items:
• Creating account on Food Delivery Application
• Gaining essential information like name, address, food items, quantity,
method of payment, etc from customer
• Preparing for order
• Delivery of order

5. Features to be tested:
• Running a Food Delivery Application
• Creating account on Food Delivery Application
• Checking user credentials
• Displaying proper content on application
• Closing the Food Delivery Application

6. Features not to be tested:

• Working with Help


• Security testing
• Interoperability testing
7. Staffing and training needs:

• knowledge and practical application of the IEEE-829 standard;


• knowledge and ability to apply in practice the basic techniques of test
design
• knowledge of various types of testing including functional and
nonfunctional.

8.Test tasks:

• Writing a test plan


• Writing test cases
• Development of criteria for the success of testing
• Conducting the testing and evaluation of the results
• Creating test reports

9. Testing tools:
• Computer: having Windows support
• Test tool: develop a test tool which can auto generate the test result to the
predefined form and automated test execution

10. Approvals:

• Team Lead
• Test engineer 1
• Test engineer 2 • Test engineer 3
• Test engineer 4

You might also like