-
Notifications
You must be signed in to change notification settings - Fork 0
Testing
Fritz Mahnke edited this page Nov 18, 2024
·
3 revisions
Repeat these test cases for new software versions.
- Inputs: Limits: 0-10, points: 0, 10, 20
- Expected results: steps: 2, error: 0
- Actual results:
- Inputs: Limits: 0-20, points: 10, 20, 30
- Expected results: steps: 2, error: 0
- Actual results:
- Enter limits in the System State area.
- Use position (relative): up to move axis to the first point.
- Press * on keypad to mark the point.
- Repeat steps 2-3 for the midpoint and maximum.
- Verify results shown are as expected.
- Use position (absolute): up to verify that the axis is currently at the maximum limit and does not move further.
- Use position (absolute): down to verify that the axis moves through the range and does not move past the minimum.
- Select position (absolute): cm. Repeat step 6 with metric units.
- Inputs: Limits: 0-10, points: 0, 10, 20
- Expected results: steps: 2, error: 0
- Actual results: steps: 2, error: 0
- Inputs: Limits: 0-10, points: 10, 20, 30
- Expected results: steps: 2, error: 0
- Actual results: steps: 2, error: 0
- position (absolute): up/down doesn't correctly move axis.
- position (absolute): cm shows max as 15, should be 10
- steps per increment is not displayed correctly before beginning calibration procedure.
- Calibration display shows garbage in steps field
- System State: ... stepsPerIncrement shows a negative value. Probably related.
- distance tracking in both up/down directions is not yet implemented.