Description
It's finally time! Sarge is ready to work on running tests within a task. At the moment, this ticket is scoped to only running tests in the task editor as we are not sending OA's to candidates yet.
Leading up this ticket, there have been a few PRs merged to help you implement this. First is the test editor #219 and the other is our polling mechanism in our Judge0 service #202. If you have any questions about either implementation ask @LOTaher or @Anzhuo-W respectively.
The goal here is to create an endpoint that calls a test runner that will poll and give back the results of the tests ALL at once. The new implementation of our Judge0 service should do this already. There are NO designs ready for this feature so this is a back-end heavy ticket, though marked as full-stack since I'd like you to implement a "run tests" button which calls your defined endpoint.
Note that the new Judge0 Connector wasn't fully tested so a good portion of this ticket should make the time to make sure it runs correctly. Ideally the "run tests" endpoint should be a route parameter (something like /api/task-templates/:id/test ??) that runs that tt's test suite. But perhaps there is a use case where our user would want to run newly created tests that aren't already defined in the schema, and if that's the case then we'll need to find a way to pass in the state of the current tests to this endpoint. This might make it a POST endpoint that accepts a body then..
Lastly, our seed data for tests are a little off. Because this is the case, our tests input and output don't properly display on the UI. The test section implementation of the editor assumed the current schema was correct, it was just the seed data. In this PR please fix that data as it will be valuable for your tests as well.
If you have any implementation questions, please reach out to @LOTaher. Once agains, no designs here right now, but there will be some feedback on Tuesday for v0 of them. For now, feel free to place the button anywhere you see fit. Could be on the top right of the test editor section.
Acceptance Criteria
- Test endpoint defined
- Tests run for edited and newly created tests even if the task template is not saved
- Basic UI to run tests
- Response should only be console logged or just have screenshots provided as we're waiting on design to implement these.
Blocked By
No response
Figma Link
No response
Mocks / Screenshots
No response
Description
It's finally time! Sarge is ready to work on running tests within a task. At the moment, this ticket is scoped to only running tests in the task editor as we are not sending OA's to candidates yet.
Leading up this ticket, there have been a few PRs merged to help you implement this. First is the test editor #219 and the other is our polling mechanism in our Judge0 service #202. If you have any questions about either implementation ask @LOTaher or @Anzhuo-W respectively.
The goal here is to create an endpoint that calls a test runner that will poll and give back the results of the tests ALL at once. The new implementation of our Judge0 service should do this already. There are NO designs ready for this feature so this is a back-end heavy ticket, though marked as full-stack since I'd like you to implement a "run tests" button which calls your defined endpoint.
Note that the new Judge0 Connector wasn't fully tested so a good portion of this ticket should make the time to make sure it runs correctly. Ideally the "run tests" endpoint should be a route parameter (something like
/api/task-templates/:id/test??) that runs that tt's test suite. But perhaps there is a use case where our user would want to run newly created tests that aren't already defined in the schema, and if that's the case then we'll need to find a way to pass in the state of the current tests to this endpoint. This might make it aPOSTendpoint that accepts a body then..Lastly, our seed data for tests are a little off. Because this is the case, our tests input and output don't properly display on the UI. The test section implementation of the editor assumed the current schema was correct, it was just the seed data. In this PR please fix that data as it will be valuable for your tests as well.
If you have any implementation questions, please reach out to @LOTaher. Once agains, no designs here right now, but there will be some feedback on Tuesday for v0 of them. For now, feel free to place the button anywhere you see fit. Could be on the top right of the test editor section.
Acceptance Criteria
Blocked By
No response
Figma Link
No response
Mocks / Screenshots
No response