Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make "Test Your Own" the front page? #67

Open
BrapiCoordinatorSelby opened this issue Feb 17, 2023 · 3 comments
Open

Make "Test Your Own" the front page? #67

BrapiCoordinatorSelby opened this issue Feb 17, 2023 · 3 comments
Labels

Comments

@BrapiCoordinatorSelby
Copy link
Member

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.

@patrick-koenig
Copy link
Collaborator

I see it that way as well.

@langeipk
Copy link
Collaborator

BRAVA was designed for these two use cases, which was (still is?) linked to the BrAPI implementition phases for breeding data resources.

  1. develop in a test environment: BRAVA test your own
  2. deploy as productive version and register in the central endpoint registry (BrAPI GITHUB) : BRAVA weekly test

The second is to deliuver a metric to data consumer and developer about the quality of BrAPI endpoints.

@BrapiCoordinatorSelby
Copy link
Member Author

@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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants