You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There might be other opinions here, but I think the primary use case for Brava is to allow people to test their own servers in a one off test. I don't know of anyone who uses the recurring weekly test data. Perhaps we should highlight the "Test Your Own" page as the primary feature.
The text was updated successfully, but these errors were encountered:
@langeipk totally agree, I just think the priority of those use cases has flipped since BRAVA was first developed, and "Test your own" should be presented first.
I think some of the other issues raised will help make the BRAVA weekly test more valuable, right now there are a lot of false negatives that need to be resolved, and its not particularly useful. I also have an item on my ever growing TODO list to pull the summary results from BRAVA and display them on the brapi.org/servers page to further deliver that quality metric
I would also add one additional use case that BRAVA should be designed for
3. Headless testing utility that can be used in automated release testing #68
Not a new idea, but if we are formalizing use cases, that should be considered in the design also
There might be other opinions here, but I think the primary use case for Brava is to allow people to test their own servers in a one off test. I don't know of anyone who uses the recurring weekly test data. Perhaps we should highlight the "Test Your Own" page as the primary feature.
The text was updated successfully, but these errors were encountered: