-
Notifications
You must be signed in to change notification settings - Fork 0
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
Image Testing 2.0 #4
Conversation
… store the tests locally instead
# Conflicts: # OpenSpaceVisualTesting/testRun.py
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very easy to run and get started 👍 Overall just some let
to const
for clarity
"difference-thumbnail", "log" | ||
] as const; | ||
|
||
const p: any = req.params; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should probably specify a type
rather than any
e.g., define
type Parameters = {
type: string;
group: string;
name: string;
hardware: string;
timestamp: string || Date || number // or w/e type this is
}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried but its gets really wordy to have any proper type information in here. Since the type
would have to be of typeof types
and then the req.params
would have to be properly parsed which would result in worse error messages.
But if there is a better way for this, I'd be happy to see and have it
|
||
|
||
|
||
# TODO: Retry openspace api connection until it works |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm thinking if this is something we should do in the API directly and then have an optional parameter in connect
to specify retries ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yea, that'd be great
Co-authored-by: Ylva Selling <ylva.selling@gmail.com>
Co-authored-by: Ylva Selling <ylva.selling@gmail.com>
Co-authored-by: Ylva Selling <ylva.selling@gmail.com>
Co-authored-by: Ylva Selling <ylva.selling@gmail.com>
This is an iteration of the previously existing image testing server. Instead of generated the webpage as the tests are finished, the application is now split up into two parts.
The backend server hosts a webpage (https://regression.openspaceproject.com) that receives candidate images and will run the image testing against a known-good reference image. If a test is new, the first submission will be the reference image, but the reference image can also be updated through the user interface.
The runner Python script can run on a multitude of machines, run tests against OpenSpace and then submit them to the backend for display.
For more information see the README.md file