Changes between Version 27 and Version 28 of LCS_specification


Ignore:
Timestamp:
08/07/2020 07:39:08 AM (6 years ago)
Author:
jdalbey
Comment:

add tests for log numbers

Legend:

Unmodified
Added
Removed
Modified
  • LCS_specification

    v27 v28  
    1717A new lane closure is created by submitting a request form.  The fields in this form are shown in the UI Prototype. Required fields are marked with an asterisk. Upon submittal the system generates a new closureID and displays a popup dialog with an acknowledgement and the form is reset. 
    1818 
    19 The new closure ID is created in the following format: The uppercase letter "T" (indicating temporary/emergency closure), followed by the highway (route) number, followed by a two letter sequence code that starts with "AA".  A log number is also required, a sequential integer starting at 1. There is a pair of Yes/No radio buttons on the form labeled "Is this an existing incident" which is defaulted to Yes, indicating this requires a new log number (increment by 1) for the closure specified by the drop down box. If No is selected than a new closure ID is created.  
     19The new closure ID is created in the following format: The uppercase letter "T" (indicating temporary/emergency closure), followed by the highway (route) number, followed by a two letter sequence code that starts with "AA".  A log number is also required, a sequential integer starting at 1. There is a pair of Yes/No radio buttons on the form labeled "Is this an existing incident" which is defaulted to Yes, indicating this requires a new log number (increment by 1) for the closure specified by the drop down box. If No is selected than a new closure ID is created. 
    2020 
    2121 4. Search 
     
    3131 6. Status Form 
    3232 
    33 When the Status Form button is clicked, a new page appear with that search result and an extra column that contains a form to update the status of the closure. The form shows radio buttons to choose 1097, 1098, or 1022 and a text field labeled "Statuser".  When the Submit Status Form button is clicked, the closure info is updated with the data from the status form, an acknowledgement message is displayed, and the Search Results page is displayed.  Note that if one of the three items has previously been chosen it will appear disabled. 
     33When the Status Form button is clicked, a new page appear with that search result and an extra column that contains a form to update the status of the closure. The form shows radio buttons to choose 1097, 1098, or 1022 and a text field labeled "Statuser".  When the Submit Status Form button is clicked, the closure info is updated with the data from the status form, an acknowledgement message is displayed, and the Search Results page is displayed. Note that if one of the three items has previously been chosen it will appear disabled. 
    3434 
    3535 7. Status History 
     
    220220|| 17e || at upper bound ||enddate= "2019-01-25" || Yes || 
    221221|| 17f || after upper bound ||enddate= "2019-01-24" || No || 
     222 
     223=== Tests for creating proper log numbers === 
     224 
     225Clear the database[[BR]] 
     226Create closure on route 1[[BR]] 
     227Expect assign id: T1AA / 1[[BR]] 
     228Create closure on route 1[[BR]] 
     229Expect assign id: T1AB / 1[[BR]] 
     230Create closure on route 1 for existing incident, select T1AB[[BR]] 
     231Expect assign id: T1AB / 2[[BR]] 
     232List to verify log number was correctly entered into the db entry.[[BR]] 
     233[[BR]] 
     234Validation:[[BR]] 
     235Fill in request form with required fields, leave "Yes" for existing incident, select no closure ID[[BR]] 
     236Expect error: Existing incidents require selecting an existing closure ID[[BR]] 
     237[[BR]]