Detailed track and segment behavior in SmartTrack mobile apps

The various combinations of tracks and segments are complicated enough that it's critical to capture the behavior for continued testing and application verification.

• SmartTrack 1.3.0 Android (or later)
• SmartTrack 1.1 IOS (or later)
• Test data from project “DevUnitTest” March 8, 2017
  • 3 tracks for vehicles “DevUnitTest-1”, “DevUnitTest-2”, “DevUnitTest-3”
  • Track DevUnitTest-1 time span 1:54 - 4:24
  • Track DevUnitTest-2 time span 2:05 - 4:23
  • Track DevUnitTest-3 time span 1:53 - 4:24
• NOTE: Developer created this test plan using a tablet set up for showing 24 hour time
  • User preferences should take effect on display.
  • Changing tablet to 12 hour display will change track and segment display times.
• Project is set to America/Los_Angeles timezone
  • Setting the tester's tablet's timezone to something other than Los_Angeles will have no effect on displayed times.
  • Times in application display must match these shown in these test results.

1. If the project is restored from archive, there will be no settings.
2. A settings file is provided: Projects/DevUnitTest/Settings/2017-03-08.settings.disabled
   1. Rename the file to 2017-03-08.settings to enable the day
   2. The settings provides two cycle lines and job hours
   3. The recommended job hours are:
      • Morning 2:00 PM
      • Lunch start 3:00 PM
      • Lunch end 3:30 PM
      • Afternoon end 4:30 PM

1. Turn off job hours for Morning, Lunch, Afternoon

• Examine stats again:

1. Turn job hours back on, with previous time settings
2. Using the playback control, set the current time to 3:15 PM
3. Insert segment break (on track ALL)
4. Using playback control, set the current time 3:14 PM (during lunch)

• Examine stats again:

1. Open the second segment from the listview (long press)
2. Uncheck “Calc Statistics”
3. Re-open the ReportView
4. Cycle through each track

• Compare entire track statistics against previous table
• Stat values must be identical

1. Make sure case 1 day settings is enabled
2. Open all 3 tracks from 3/8
3. Disable calc on tracks 2 & 3

• Resulting statistics should look like

1. Make sure case 1 day settings is enabled
2. Open all 3 tracks from 3/8
3. Segment ALL at 3:15
4. Disable calcs segment two from 3:14 to 4:30

• Verify stats

1. Make sure case 1 day settings is enabled
2. Open all 3 tracks from 3/8
3. Segment each track (DUT-1, DUT-2, DUT-3) at 3:15
4. Disable calcs on second segment of each of three tracks.

• Verify stats as:

1. Make sure case 1 day settings is enabled
2. Open all 3 tracks from 3/8
3. Segment ALL at 3:15
4. From view list, disable statistic calcs on first segment (2:00 - 3:15)
5. Segment each track (DUT-1, DUT-2, DUT-3) at 4:00
6. For each track (DUT-1, DUT-2, DUT-3) disable statistics calculation in last segment (4:00 - 4:30)
7. Open play and report
8. Manually scan time from start to 3:15

• Verify that report indicates “Statistics disabled”
• Verify that report begins reporting statistics at “post lunch” period.

1. continue time scanning until 4:00

• verify that statistics are:

1. continue time scanning from 4:00 through end of day

• Verify that statistics hold constant from 4:00 to end of day
• Verify that each track summary (from view list) is consistent with track segment 2 summary.

These tests will detail creation, deletion, and modification of segments. This is not a statistic centric test. Make sure any day settings are disabled by appending “.disabled” to any active settings files in AgtekAccess (for this project only

Generic setup

1. Re-open the three tracks for this test project
2. Open the playback window

1. Using the playback control, set the time slider to 3:15
2. Insert a segment using the on-screen scissors button
3. Verify new segment line at 3:15 in the playback view

• Verify the two segments in the list view

1. Using the track selector cycle through each track

• Validate that the 3:15 segment break is present in the playback control

1. Set the job hours on the project to be
   • Day start at 2:00 PM
   • Day end at 4:30 PM
2. Validate that the start time on the first segment is now 2:00 PM

• Validate that the end time on the second segment is now 4:30 PM
• Validate that the end times on the playback view are adjusted to match the new job hours.

1. Open the view list
2. Delete the first segment in the list
3. Reopen the playback control

• Validate that the segment break at 3:15 is gone, from ALL and each track

1. Segment ALL track at 3:15 PM
2. Using the track selector, choose DevUnitTest-2
3. Segment that track at 4:00 PM

• Validate a new segment line at 4:00PM for track DUT-2
• Validate that the new segment line is not present for any other track
• Validate that track DUT-2 has three segments in the view list

1. Re-open the View list
2. Delete the first 2:00 to 3:15 segment on ALL
3. Close view / re-open view

• Verify that ALL segments are missing and DevUnitTest-2 still has 3 segments

  2:00 PM - 3:15 PM
  3:15 PM - 4:00 PM
  4:00 PM - 4:30 PM

Occasionally apparently strange things happen, but once they are explained the amount of strangeness is reduced. These tests expose the strangeness in the system.

Segmenting a day in the middle of active cycles can cause a reduction in the cycle count. This is because segments are defined to be separate periods of work. Thus if a segment happens to occur just before a point in time, when the track would cross the cycle line, the total cycle counts will be reduced. Introducing new segments alters total statistics. This is expected by the definition of segments.

1. Enable settings for 3/8 by removing “.disabled” from the end of the settings file (via Agtek Access)
2. In ST, open all tracks for DevUnitTest on 3/8
3. Verify the background file, and two cycle lines
4. Open Report-View and verify 57 cycles (3*9 morning + 3*10 afternoon)
5. Open Playback, select track selector for ALL
6. Segment ALL at 2:24
7. Either close playback, or time select to end of day.
8. Verify that the report is now showing 54 cycles.