Programming Question

INSTRUCTIONS
Review the followingReview the following websites on the Internet (URLs may have been updated since this writing):http://www.tutorialspoint.com/software_testing/sof…
http://www.exforsys.com/tutorials/testing.html
https://www.softwaretestingclass.com/wp-content/up…
https://microtoolsinc.com/papers/how-test-plan/

Describe the objective and the scope of your test plan. Fully describe the functions that will be tested and those that will not be tested.
Provide sufficient justification on why or why not certain functions will be tested.

Describe your testing methodology.
Describe the test environment that will be used to validate the functionality of the project. Describe the advantage and disadvantages of the test environment you will use.
Describe any specific test equipment that will be required for testing.
Provide a test schedule that corresponds to your current project plan. Include both internal (team) testing of the product, as well as testing that includes your customer (user acceptance testing).
Identify the phases of your test cycle and describe any dependencies between each test phase (i.e. what must be tested successfully prior to you moving to the next phase?).

Create test scripts for each test to be performed. See Assignment 10-T Test Results / Final Test Scripts for details on how Test Scripts should be formatted. For those tests where you do not have enough details to complete the sample test script, not that clearly. (Please note: this is the majority of this assignment.)
Describe how you plan to monitor and control the testing schedule.
Identify which team members will be responsible for testing the different functions of your project.

GUIDANCE
There are great test plans and there are good test plans. Your goal is to ensure that you have developed a “good enough” test plan for your project that will meet the basic requirements of the project. Remember that often times the “great” test plan requires a lot of work to complete, but the value is low – you expend a lot of effort to create something that would be just as useful if you had expended half of the effort. Our goal here is to work smarter, not harder. The KISS (keep it simple stupid) principle is very valid here. We all have too much work to do to make everything pretty – you must make your test plan functional and viable.
You need to (a) identify what you are going to test, (b) why you will test, (c) how you will test, and (d) the schedule of the test. It is important that the test plan follows the schedule of the overall project plan (for example, you cannot schedule the testing of the login screen in your test plan in week 2 of the project, if it will not be developed and ready for testing until week 4 according to the project or development plan).
Our goal here is to get the project done, and we are not looking for excellence, but are looking for viable, functional, and reasonable test plans that have a positive impact on the project. Do not overdo the assignment but ensure that your response to this assignment adequately addresses the needs to test functionality. Follow the grading dimensions in the grading rubric to achieve full credit for this assignment.
Please ensure that you address the functional requirements of your project in your test plan. The article “How to Write a Great Software Test Plan” at the following URL: https://microtoolsinc.com/papers/how-test-plan/ provides excellent guidance on what should be included in the test plan.
For Assignment 6, provide the following:
Title page with your name, assignment, date.
Use the Assignment Instructions above as a guide for your response.
Review the rubric in Blackboard for evaluation on grading.