knightbk/Junior-Project-Mobile-Student-Lookup — Issue #16: Acceptance test plan
Author: vitalema
Created: 2012-02-01 19:06:15+00:00
State: open

Update your acceptance test plan from CSSE 371 as necessary based on changes to your analysis and design this term. Use the format that you used for this test plan in 371. This plan will be used for some of the demonstration in task #7. The plan may now be in part an integration and acceptance test plan:

a.	Integration tests: We want to go light on the integration part here, because you have limited time left this term, but you may need a little of this. Integration testing is the name for ways to test the interfaces and other ways the parts of your system interact. It is a major part of "white box testing," the part that builds on unit testing. If you are an SE major, you'll see more of this in CSSE 375. We don't want you to go overboard on testing the internals, but please do so when it's necessary to show that partly developed features work. This would be especially true of parts of the system that you cannot see from the GUI. We are not expecting an industry strength integration plan here, but it should serve as a guide for us to watch your demo that shows from the code how the design has been implemented properly.

b.	Acceptance tests: These are main tests. They likely will show that everything works from the GUI as the user would operate the system. However, it may also show other things - e.g., if the user needs to verify that the data in the database is correct.