While cleaning up the tests is there any value in splitting out tests
that are redundant
- test that test low level functions whose failures will be picked up in
other tests of higher level functions
- tests that are run on modules that "never" change.
The lower level test may still be useful f
Hi Marc-Aurèle, (and everyone else)
The title probably is slightly incorrect. It should really say known Marvin
test failures. Trillian is the automation that creates the environments to run
the tests in, the tests are purely those that are in Marvin codebase so anyone
can repeat them. In fa
Hi Marc,
You've raised a very valid concern. When we've known list of smoketest
failures, it's understandable that most people may not understand how to
interpret them and ignore them. Access to the Trillian environment is another
issue. I don't have all the answers and a solution ot these pro
