search

mosaicworld / vb

TEAM BVB app
0 stars 0 forks source link

Usability of Number of Courts button #8

Open mosaicworld opened 10 years ago

mosaicworld commented 10 years ago

This button was created b/c in the court assignment process for my current volleyball group, we usually first decide how many courts will be necessary to accommodate the players. However, it might be more practical to ask the user, how many courts are available (2, 3, 4, 5, unlimited) b/c that might cause a greater issue.

mosaicworld commented 10 years ago

The results of this button is probably not that helpful to the end-user. Although the interim calculations are necessary for the results of the 2nd button. The display that results from the 2nd button is somewhat redundant with information displayed as results from the 1st button. Writing up the functional test cases made the redundancy more obvious. But there is an issue where the text results from the number of courts button is more easy to automate testing for than the html5 canvas (visual) results from the random teams button.

mosaicworld commented 10 years ago

The user only cares about the results from the 2nd button (Get random teams). But the program requires info from the 1st button (Get Number of Courts) in order to compute the results for the 2nd button. Also QA's automated tests needs the results from the 1st button, since the results from the 2nd button are currently a bit challenging to automate testing for (HTML canvas, plus randomly calculated results). Probably need to get rid of the first button; keep all computations in their current order but link all computations to the 2nd button (Get random teams).

mosaicworld commented 10 years ago

Note that proposed changes to number of buttons on form would impact QA tests (for visual testing and automated testing).