> Eh, it's OK, just seems slightly inconsistent to be specifying > environment 'horizontally' for some tests and 'vertically' for others. > Why not just another table with the two tests that use the GUI/text > distinction and those as the columns? Hmm, I guess there were two reasons: 1. I didn't actually consider text vs gui to be environments, it seemed similar to me as with Testcase_install_repository_NFS_graphical and Testcase_install_repository_NFS_variation. The difference was that I didn't want to create two separate test cases when the steps are almost exactly the same, so I tweaked the description slightly to accommodate for both approaches and then differentiated it just in the test case title in the table. You can also see this approach in the Desktop matrix with the Testcase_desktop_updates (installation) and Testcase_desktop_updates (notification) test cases. 2. When I did the above, I probably still had some architectures as environments. So I needed to do it like this, otherwise I would have a table with three dimensions, which is a bit hard to create :) Afterwards, I removed that architectures (moved some test cases into a separate table), and I ended with just a Result column. So now, yeah, we can definitely move gui and text to be columns, as environment. But we will need to create yet another table (just for those two test cases), which I wanted to avoid (multiple rows are probably a bit easier to read when in the source view than multiple tables and/or columns). But either way is fine with me. We can also consider to remove those "text" test cases, because I have in fact added them myself, without any discussion, it just seemed right to me. Before my change, we tested it on x86 and ARM, which kind of implied gui and text, but not necessarily. It seemed logical to remove those architectures and replace it with their real difference, which is gui and text. But maybe people might not see their importance high enough to justify this separation. > > With a very neat-freak hat on, I'd probably have put the table with just > one column either at the top or bottom, not in the middle - just flows a > bit odd visually for me. But that's very small beans. I tried to sort that according to milestone priority, so that tables containing Alpha test cases are above tables containing Beta+ test cases. No objections to change it. > > (I am pleased to note that relval testcase-stats seems to handle the > changes well :>) Great, it flashed through my mind, but I forgot about it afterwards. -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
