01219245/manual testing - ประวัติรุ่นแก้ไข

Jittat: /* Testing result */

2014-04-30T07:30:30Z

Testing result

2014-04-30T07:29:09Z

Testing result

2014-04-30T07:22:02Z

Testing result

2014-04-30T07:20:15Z

Testing result

2014-04-30T07:19:08Z

Test cases

2014-04-30T07:06:00Z

Test cases

2014-04-30T06:13:58Z

Feature list

2014-04-30T06:13:10Z

Test cases

2014-04-30T06:07:52Z

Test case template

2014-04-30T05:59:06Z

Feature list

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 07:30, 30 เมษายน 2557
แถว 56:		แถว 56:

	For the failed test cases, you should put enough information so that the developer can '''reproduce''' the failure. Otherwise, the developer will not be able to fix these problems.		For the failed test cases, you should put enough information so that the developer can '''reproduce''' the failure. Otherwise, the developer will not be able to fix these problems.
		+
		+	[[Image:01219245-test-results.png]]

	== Exploratory testing ==		== Exploratory testing ==

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 07:29, 30 เมษายน 2557
แถว 54:		แถว 54:

	'''Practice:''' You start with the test case list. For each test case, perform the steps as described in the test case. If the actual result is as expected, that test case passes, otherwise it fails. Put this testing result on a new sheet on the Google document.		'''Practice:''' You start with the test case list. For each test case, perform the steps as described in the test case. If the actual result is as expected, that test case passes, otherwise it fails. Put this testing result on a new sheet on the Google document.
		+
		+	For the failed test cases, you should put enough information so that the developer can '''reproduce''' the failure. Otherwise, the developer will not be able to fix these problems.

	== Exploratory testing ==		== Exploratory testing ==

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 07:22, 30 เมษายน 2557
แถว 52:		แถว 52:

	After you design all the test cases, you (the tester) and your friend (the developer) should agree on the test cases. Then it's time to perform the testing.		After you design all the test cases, you (the tester) and your friend (the developer) should agree on the test cases. Then it's time to perform the testing.
		+
		+	'''Practice:''' You start with the test case list. For each test case, perform the steps as described in the test case. If the actual result is as expected, that test case passes, otherwise it fails. Put this testing result on a new sheet on the Google document.

	== Exploratory testing ==		== Exploratory testing ==

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 07:20, 30 เมษายน 2557
แถว 50:		แถว 50:

	== Testing result ==		== Testing result ==
		+
		+	After you design all the test cases, you (the tester) and your friend (the developer) should agree on the test cases. Then it's time to perform the testing.
		+
		+	== Exploratory testing ==

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 07:19, 30 เมษายน 2557
แถว 48:		แถว 48:

	[[Image:01219245-testcase-templates.png]]		[[Image:01219245-testcase-templates.png]]
		+
		+	== Testing result ==

@@ แถว 36: / แถว 36: @@
   Feature No: ________________
   Test case No: ______________
-  Goal: ______________________
+  Description/Goal: ______________________
   Steps:
 . ________________
@@ แถว 45: / แถว 45: @@
 You need to keep feature numbers and test case numbers so that you can refer to it later.
-'''Practice:'''
+'''Practice:''' On the google spreadsheet, create a new sheet called "Test cases", and put the test cases in that sheet.

@@ แถว 13: / แถว 13: @@
 * After the Gozilla is hit, new one appears at a random position.
 * If the player fire 5 cannon balls and still miss the Gozilla, the game is over.
 Create a Google Doc Spreadsheet document and put these features in one of the sheet.

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 06:13, 30 เมษายน 2557
แถว 30:		แถว 30:
	For each of the features, try to come up with happy test cases (a few would be great) and at least one unhappy test case.		For each of the features, try to come up with happy test cases (a few would be great) and at least one unhappy test case.

−	You should write down the test case into the following template:	+	You should write down the test case into the following template (see spreadsheet example at the end):
		+
		+	Feature No: ________________
		+	Test case No: ______________
		+	Goal: ______________________
		+	Steps:
		+	1. ________________
		+	2. ________________
		+	3. ________________
		+	Expected result: __________________
		+
		+	You need to keep feature numbers and test case numbers so that you can refer to it later.
		+
		+	'''Practice:'''

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 06:07, 30 เมษายน 2557
แถว 18:		แถว 18:
	[[Image:01219245-feature-list-sheet.png]]		[[Image:01219245-feature-list-sheet.png]]

−	== Test case template ==	+	== Test cases ==
		+	For each of the feature in the list, we shall think about how to verify that the software actually delivers that functionality. The best way to demonstrate that is to test it. To test the software, you can just sit at the computer with the software and then play with it: this is called exploratory testing. Today, we will focus more on a traditional type of software testing; people sometimes refer to this is scripted testing.
		+
		+	We will look at each feature and think about the steps we have to perform to demonstrate that the feature is working and write those steps down. The activity you are doing is called ''test case design''. Then, someone (hopefully, you) will take the test cases and perform the testing.
		+
		+	Usually, for each feature we might be able come up with two types of test cases:
		+
		+	* Happy test case: this type of test cases demonstrate the successful situation.
		+	* Unhappy test case: this type of test cases demonstrate the exceptional situations, i.e., when things do not go according to the plan.
		+
		+	For each of the features, try to come up with happy test cases (a few would be great) and at least one unhappy test case.
		+
		+	You should write down the test case into the following template: