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

feat: Find Failing Testcases for Atcoder Problems #1488

Open
IamMahfooz opened this issue Oct 2, 2024 · 1 comment
Open

feat: Find Failing Testcases for Atcoder Problems #1488

IamMahfooz opened this issue Oct 2, 2024 · 1 comment

Comments

@IamMahfooz
Copy link

Problem:

Users generally discard their initial approach and move on to the editorial upon failing to debug the failing testcases.

Proposed Solution :

Integrate stress testing feature to 'Atcoder Problems' website to make it a one stop solution for accessing and debugging their submitted solution. I have created a working demo of the feature at https://atcoder-stress-test.vercel.app/ and can work on integrating the fronted to Atcoder Problems website ( backend hosted on render free service ).

@IamMahfooz
Copy link
Author

@kenkoooo please take a look .

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

No branches or pull requests

1 participant