Changes between Version 2 and Version 3 of LCS_specification
- Timestamp:
- 04/02/2020 10:27:06 AM (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
LCS_specification
v2 v3 48 48 direction - traffic direction, see options in combobox. 49 49 50 facility - what part of the roadway is affected, see options in combobox. 50 facility - what part of the roadway is affected, see options in combobox. 51 51 52 startdate - calendar date when the closure will begin. The user enters MMDDYYYY but the value stored in the database must be YYYYMMDD. 52 startdate - calendar date when the closure will begin. The user enters MMDDYYYY but the value stored in the database must be YYYYMMDD. 53 53 54 enddate - calendar date when the closure ends. The user enters MMDDYYYY but the value stored in the database must be YYYYMMDD. 54 enddate - calendar date when the closure ends. The user enters MMDDYYYY but the value stored in the database must be YYYYMMDD. 55 55 56 starttime - time of day on the start date when the closure begins. Format: HHMM (military time) 56 starttime - time of day on the start date when the closure begins. Format: HHMM (military time) 57 57 58 endtime - time of day on the end date when the closure ends. Format: HHMM (military time) 58 endtime - time of day on the end date when the closure ends. Format: HHMM (military time) 59 59 60 startcounty - County in which the closure starts. For now, Orange county is the only option. 60 startcounty - County in which the closure starts. For now, Orange county is the only option. 61 61 62 endcounty - County in which the closure ends. For now, Orange county is the only option. 62 endcounty - County in which the closure ends. For now, Orange county is the only option. 63 63 64 startlocation - Cross street used to identify location of the closure. The options in the drop down are obtained from the postmile book. It would be nice if the drop down was smart enough to only display cross streets on the selected route. 64 startlocation - Cross street used to identify location of the closure. The options in the drop down are obtained from the postmile book. It would be nice if the drop down was smart enough to only display cross streets on the selected route. 65 65 66 66 endlocation - same as above. closuretype - see options in combobox. 67 67 68 worktype - see options in combobox. 68 worktype - see options in combobox. 69 69 70 estdelay - estimated number of minutes of delay caused by the closure. (How long drivers have to wait). 70 estdelay - estimated number of minutes of delay caused by the closure. (How long drivers have to wait). 71 71 72 tmpcozeep - yes or no 72 tmpcozeep - yes or no 73 73 74 tmpdetour - yes or no 74 tmpdetour - yes or no 75 75 76 supervisor - see options in combobox. obtained from callout map. 76 supervisor - see options in combobox. obtained from callout map. 77 77 78 fieldrep - same as above. 78 fieldrep - same as above. 79 79 80 meetingplace - optional, free format field. 80 meetingplace - optional, free format field. 81 81 82 reason - optional, free format field. 82 reason - optional, free format field. 83 83 84 84 remarks - optional, free format field. … … 87 87 88 88 s1097date s1097time s1097user s1097phone s1098date s1098time s1098user s1098phone s1022date s1022time s1022user s1022phone 89 90 == Test Plan == 91 See Reference: [http://users.csc.calpoly.edu/~jdalbey/205/Resources/bbtestLec.html Equivalence Classes] 92 93 ==== Valid Equivalence Classes ==== 94 V1: closureid not empty, all others empty 95 96 V2: closureid, log num not empty, all others empty 97 98 V3: route not empty, all others empty 99 100 V4: direction not empty, all others empty 101 102 V5: start date not empty, all others empty 103 104 V6: end date not empty, all others empty 105 106 V7: start date not empty, end date not empty, all others empty 107 108 ==== Invalid Equivalence Classes ==== 109 X2: log num not empty, closureid empty 110 111 ==== Boundary Value Analysis ==== 112 Given a closure with a start date of Jan 2, 2020 and end date of Jan 5, 2020 provide input data of Jan1, Jan2, Jan 3, Jan4, Jan5, and Jan 6. 113 114 ==== Branch Testing ==== 115 Since search by any combination of fields is allowed, for exhaustive testing we would do each of the 7 classes above in combination with the others, but that would require 7! = 5040 tests. To simplify, we will provide tests for each field included in one combination with some other field. 116 117 1. ClosureID and log number (Note that in general use when a closure id and log number are provided the other fields will NOT be provided because closure id/log number specifies a unique closure.) 118 119 2. route and direction (Note that in general use direction won't be provided without a route, though it is legal to do so.) 120 121 3. route and start date 122 123 4. route and end date 124 125 5. route and start date and end date 126 127 For each of the above cases, we want a search that succeeds and a search that finds no results.
