On Wed, 2018-10-31 at 13:37 -0400, pmkellly(a)frontier.com wrote:
> In regard to the test results page and the specified order of testing:
> Following up on a comment I made on a message earlier today concerning
> if the updates-testing repo should be enabled for Anaconda installs and
> the impression I am under that we want to do testing on each drop
> according to this matrix before any updates are applied I edited the
> subject page to move the Updates Graphical test to be the last test in
> the Beta sequence.
The matrices aren't intended to be organized in any kind of sequential
order, really. But changing that wouldn't hurt anything, sure.
> I searched for the source of the matrix, but could not find it. Then I
> considered that that each matrix may be made by editing the last one.
No, you were right the first time. The template page is here:
please be very careful about editing these, though, as you could easily
break a lot of stuff. Ideally, please propose changes to the list
before making them, and certainly mail the list if you do change
I'll make this change in the template now, since it should be safe and
might help someone. Thanks!
> That's why I edited this page at least to get the suggestion going.
> I would further suggest that we add a command line DNF test at the end
> of the final sequence, but I did not add such a test to the page.
That is in Base, not Desktop, as it is not desktop-specific.
- note that
has 'package_install_remove' and 'update_cli' tests.
Thank you. I was just thinking that lots of folks tend to start at the
top of a list and proceed down. I am certainly one of those. This seemed
like a simple way to help avoid circumstances where a problem/bug is
caused by an an unstable update rather that being in the actual drop
being tested. My lab course instructors always taught me "If you want
accurate results only test one thing at a time and only change one
variable at a time". I imagine that software folks get similar lessons,
but it's easy to forget. Also, a new kid on the block may not have any
experience in testing and not even be aware of things that can cause
them problems with false failures.
Have a Great Day!