Software Testing of classroom exercises

One: Test plan:

1. Perform the functional test first:

(1) Unit test-verifies the correctness of the program on the lowest function /parameter.

(2) Function test-Verify the function of each module.

(3) Integration testing-Verify the functionality of several interdependent modules.

(4) Scene test-Verify that several modules are able to complete a user scenario.

(5) System test-test for the entire system function.

(6) The external software Testers thoroughly test the software in the actual user environment.

2. Re-test on non-public energy:

(1) the test software can work properly under load condition.

(2) test the effectiveness of the software.

(3) Compatibility test.

(4) configuration test-test software can work properly under various configurations.

(5) usability test-test software is good to use.

(6) Software security testing.

Two: Do we need to test until our software is perfect?       Testing is a must, but can not be required to achieve absolute perfection, because no software PRODUCT is perfect, try to make users feel "perfect" on it. Three: What is "good enough" for testing? What is the "standard for Exit"? From the user's point of view, let the user to your software PRODUCT function recognition is "good enough". "Exit Criteria" is from the user's point of view, your software product features can provide users with good experience and use value. Four: Our beta version is "good enough" definition1. Login can be registered as normal. 2. You can perform the necessary operations on the data. 3. To meet the user's common functions of the implementation. 4. It is easy for users to use. V: Test matrix

	User Type	Screen Resolution	Operating system	Operating system Default language	Network speed	Browser	Combination Total
Number of variables	3	3	3	3	3	3	18
	User	1024x768	Win7	Chinese (simp.)	Internet	Firefox
	Browse by	1280x768	Win8	Chinese (simp.)	Adsl	IE10
	Administrator	1366x768	Win7	Chinese (simp.)	Lan	Sogou

Software Testing of classroom exercises