Please provide an option to download the entire testcase like CSES. As of now testcases are just partially visible.
№ | Пользователь | Рейтинг |
---|---|---|
1 | tourist | 3947 |
2 | jiangly | 3734 |
3 | Radewoosh | 3646 |
4 | jqdai0815 | 3620 |
4 | Benq | 3620 |
6 | orzdevinwang | 3612 |
7 | ecnerwala | 3581 |
8 | Geothermal | 3569 |
8 | cnnfls_csy | 3569 |
10 | ksun48 | 3479 |
Страны | Города | Организации | Всё → |
№ | Пользователь | Вклад |
---|---|---|
1 | awoo | 162 |
2 | maomao90 | 160 |
3 | nor | 157 |
4 | atcoder_official | 156 |
4 | cry | 156 |
6 | adamant | 155 |
6 | -is-this-fft- | 155 |
8 | maroonrk | 154 |
9 | Petr | 146 |
10 | djm03178 | 145 |
Please provide an option to download the entire testcase like CSES. As of now testcases are just partially visible.
Название |
---|
Hey you can use methods like stress testing to find the test case you are failing. But yeah codeforces should give you the testcase you are failing.
Also I think that lets say even when you get the testcase you are failing it wont be of much use to u if it is large testcase as you wont be able to run it down on a notebook to figure out what went wrong.
Instead make generators with small constraints to at least check if you're approach is correct. Then you may proceed to test on larger inputs.
Errichto Video
similar video in Hindi
I also face the same problem. Sometime I can see error in a particular test case but the test case is too large to see. There should be more flexible options so that we can debug more efficiently.
Codeforces may also use systems like LightOJ so that we can compare the result the whole test case results with an accepted one.