Status Report #1 Acceptance Testing

Date: 22.05.2018

1. Status

• 1.1 In our weekly meeting ;the meaning of acceptance test is discussed
• 1.2 10/10 members directly contribute to the acceptance tests and some people take the responsibilty of prepearing the cases.
• 1.3 The team tried open issues and discuss the development process.
• 1.4 The requirenment analysis scanned again and again.
• 1.5 The test case format and the platform decided after the analysis and scan part.
• 1.6 The assumption of each test cases are decided.
• 1.7 The scenerio of test case contains : 1-Test step number 2-Test step description 3-Test data 4-Expected result 5-Actual result 6-Pass/Fail.
• 1.8 The 6-Pass/Fail will happen after the real tests of our implementation.
• 1.9 The twenty-one acceptance test cases prepared and ready for the test.

2. Acquirements

• 2.1. The most of team members utilized GitHub for the first time and attend a real project.
• 2.2 The notion of Test cases are discovered
• 2.3 Some real up and useful test cases created at the end.

3. Difficulties

• 3.1. The acceptance test case preparation is hard because the project is in progress.In real life as all know that the plan and the test cases should be prepare before project's end.So it is a hard part for us to prepare and very thoughtful.

• 3.2. It created the obligation to regularly check and correct the Requirenment Analysis.We actually prepare the acceptance test 2 weeks.Second, this fact made the Requirenment Analysis feel like a burden rather than a guide on how we will develop our software.

• 3.3. Actually, we dont know this cases are pass or fail after the real test case happen.So it is a food for thought for us.

• 3.4. We have learned what the important aspects of test cases, what are the logic behind them and how to use them.

4. Suggestions

• 4.1. Next year, we will be starting to develop the real thing, to write the code. Which –surely there will be differences but- is a process we are more familiar with than the tasks we worked with this semester. Thus, it may be easier to produce a more realistic plan and use it without modifying it every 3 weeks. Furthermore, because our job will demand even more collaboration and communication, after all of these we test our prepared cases. Thus we must –even if the same difficulties persist- find a way to make it useful and we must follow it.

• 4.2. While we are doing implementation we should be aware of the testing them.The acceptance test should be pass.This is the reason why we prepared them before the job finished.