Summary and reflections report
Your summary and reflections report should be a paper documenting your decision making and the results of your software testing as well as your reflections upon your lessons learned by drawing connections to the principles discussed in the course. Specifically, the following critical elements must be addressed:
I. Summary
A. Describe your unit testing approach for each of the three features.
i. What was your level of testing (i.e., number of tests) for each of the features? Explain why your level of testing was appropriate based on what you have learned about testing best practices in the course.
ii. How did you organize your tests (e.g., grouping tests into test suites) for each of the features? Explain why your organizational strategy was appropriate based on what you have learned about testing best practices in the course.
iii. To what extent was your approach aligned to the software requirements? Support your claims with specific evidence from the test plan.
B. Describe your experience writing the JUnit tests.
i. How did you ensure that your code was technically sound? Cite specific lines of code from your tests to illustrate.
ii. How did you ensure that your code was efficient? Cite specific lines of code from your tests to illustrate.
C. Defend the overall quality of your JUnit tests. In other words, demonstrate that your tests were effective in finding the errors. Cite the specific number (at least five are required) and nature of the errors found.
II. Reflection
A. Testing Techniques
i. What were the software testing techniques that you employed in this project? Describe their characteristics using specific details.
ii. What are the other software testing techniques that you learned about in this course? Describe their characteristics using specific details.
iii. For each of the techniques you discussed, explain the practical uses and implications for different software development projects and situations.
B. Test Management Practices
i. Now that you have experienced the testing side of software development, assess the importance of properly managing software testing. What are the risks of not appropriately verifying and validating your code? Support your claims with specific evidence and principles discussed in the course.
ii. Analyze the major components of administrating testing that must be considered and implemented in order to ensure software quality. In other words, what are the best practices you have learned regarding testing strategy, planning, and monitoring? Illustrate your response with specific examples and principles discussed in the course.
iii. Finally, identify the types of tools and technology available for implementing testing strategies. For example, to what extent can automation be used to support quality software development? Illustrate your response with specific examples discussed in the course.
C. Mindset
i. Assess the mindset that you adopted working on this project. In acting as a software tester, to what extent did you employ caution? Why was it important to appreciate the complexity and interrelationships of the code you were testing? Provide specific examples to illustrate your claims.
ii. Assess the ways you tried to limit bias in your review of the code. On the software developer side, can you imagine that bias would be a concern if you were responsible for testing your own code? Provide specific examples to illustrate your claims.
iii. Finally, evaluate the importance of being disciplined in your commitment to quality as a software engineering professional. Why is it important not to cut corners when it comes to writing or testing code? How do you plan to avoid technical debt as a practitioner in the field? Provide specific examples to illustrate your claims.
