Hi Jason, Thanks for the update. Your proposal below to select a subset of timezone from a dynamically generated list sounds good. One suggestion I have with this approach is to have the algorithm that randomly select the timezones to be sure to include timezone strings that are long. The text installer assumes the screen is 80 columns. So, we want to make sure that those timezone strings that are long get displayed correctly.
Thanks, --Karen Jason Zhao wrote: > Hi, Karen, > > To re-consider the test cases, the requirement for this case should be > updated according to your comments. Following is the possible issues and > solutions. > > ISSUE 1. > The definite limited time zone list: > The initiative of the static time zone list was because the tests should > cover limited time zone combination, that was why a static time zone > list was set up. However, the defect of the static list is the test is > only able to test the items on the list, for other time zone > combinations, the test could not and will not cover. > > SOLUTION: > The better solution is to sample limited time zone combinations by > random, on each Time Zone Regions/Locations/time zone, the test could > sample 50-60 different time zone combinations by random, then check the > result on "Summary" screen. > > ISSUE 2: > the time zone list is static: > On the time zone list, every items are pre-determined and hard-coded, > once the system has any changes, the test case should be updated manually. > > SOLUTION: > The better solution is to dynamically generate the test list by invoke > functions of libzoneinfo.so. > > On the conclusion, > The test will write a program in C or Python, which will invoke > libzoneinfo.so to dynamically generate test list, and the test list is > the 50-60 combinations of time zones which are picked up by random. Then > check the 50-60 combinations on "Summary" screen. In this way, there is > no need to set up a static list and whole time zone combination can be > covered by testing in the long run. > > Please tell me your idea. > > Thanks > Jason > > <snip> > >>>> Jason Zhao wrote: >>>> >>>> >>>> >>>> >>>>> Hi, Sue, Keith and Karen, >>>>> >>>>> Per last meeting yesterday, I will write a test-supported time zone list >>>>> to you. Please review it in attachment. >>>>> The reason of the list is because there are thousands of selection pairs >>>>> and it will time-consuming for testing to iterate all the items and >>>>> verify one by one. >>>>> >>>>> Currently, there are totally 50 pairs on this list, please review it to >>>>> see if it is enough. >>>>> >>>>> Africa: 5; >>>>> Americas: 12; >>>>> Antarctica Ocean: 1; >>>>> Arctic Ocean: 1; >>>>> Asia:9; >>>>> Atlantic Ocean: 2; >>>>> Australia: 2; >>>>> Europe: 12; >>>>> Indian Ocean: 1; >>>>> Pacific Ocean: 5 >>>>> >>>>> >>>>> Request: >>>>> On this list, since I don't know what the expected result for each >>>>> selection pair(Region/Location/Time zone) so I mark them with "?". During >>>>> test, we will verify the result one by one on "Installation Summary" >>>>> screen. Since summary page is not finished, yet and we don't know what >>>>> the expected result will be, would you please tell what are the exact >>>>> results or how to get the results. Thanks! >>>>> >>>>> Question: >>>>> Currently, on the "Time Zone" screen after selection of "Pacific >>>>> Ocean/United States", there are a lot of items inside, including "Eastern >>>>> Time", "Central Time".... Do you think it is correct? I mean on "Pacific >>>>> Ocean" region, the "United States" location should only contain several >>>>> time zone, not the whole list of time zone of "United States". E.G., the >>>>> "Eastern Time" should be at the other side of "Pacific Ocean" across >>>>> American continent, and it will be inappropriate to be here. >>>>> >>>>> >>>>> Thanks >>>>> Jason >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> >>> >>> >>> >> >> > >
