Description
Step 1: Complete Construction
You started programming the system last week. Before we can continue with the final labs, you must complete your code. Do not worry about getting it perfect. Having some defects will actually help in next week’s lab. For now, just get the code written so that it compiles, runs, and contains code to support all intended features of the system.
Step 2: Complete a Set of Detailed Test Cases
One of the largest and most important artifacts in the testing effort is the set of test cases. For each major feature of the system, complete the test case template to summarize the test, describe how to conduct it, and explain the success criteria. Next week, you will be following these test cases and reporting on your findings, so make sure that your testing instructions and criteria are complete and clear. This is another example of how more careful work up front leads to easier, higher quality work later.
The following is a brief explanation of how to create a test case based on elements of the IEEE Standard 829 template. The structure of your test cases can be whatever readable form you would liketables, bulleted lists, paragraphs, some combination of these, or whatever you feel works best, as long all of this information is present and easy to read. Complete a separate test case for each feature (class/program or unit of code) of your system.
Remember This
You can have multiple test cases per class (program or unit of code) in the system. A test case should be detailed enough such that the person who executes it does not have to be the author or creator of the program code. There is enough information in the test case details that the feature (program code) can be tested by another team member.
Test Case Template
- Test Case Creator: The name of the person writing this test case
- Tester Name: The name of the person performing this test
- Test Date: The date that this test was performed
- Test Identifier: A unique ID assigned to this test case to aid in communication and traceability
- Requirements Addressed: Which requirements from the IEEE 830 SRS requirement list are included in this test
- A test case can involve more than one requirement, and a requirement can be tested in more than one test case.
- Prerequisite Conditions: What must be true before this test begins, such as what state the application is in or what actions must have already taken place
- Test Input: Identify all inputs required to execute this test case.
- Expected Test Results: Specify what the results should be if this test is successful.
- Criteria for Evaluating Results: Explain what factors could be used in making a determination of whether this test has succeeded or failed.
- Instructions for Conducting Procedure: Write a step-by-step script explaining exactly how to perform this test.
- Features to Be Tested: List the features of the software that are involved in this test.
Here are a few videos to help you get started:
Video Title: Connecting Access to C#
Video Title: Connecting SQL Server to C#
Video Title: Connecting Access to Java
Video Title: Connecting SQL Server to Java
Video Title: Creating a JTable
