You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, all test cases are named in one format test$$.in. However, it's quite hard to track which one is in which subtask or which one is an edge case. For example, it is great if we can name them like big$$.in and small$$.in with some configs. I would prefer if the configs are put in tests.sh because it's much easier to manage all test cases there. It already has the hashtag line to separate subtasks, what about putting another line right below for the name (use the default config if empty)?
The text was updated successfully, but these errors were encountered:
Currently, all test cases are named in one format
test$$.in
. However, it's quite hard to track which one is in which subtask or which one is an edge case. For example, it is great if we can name them likebig$$.in
andsmall$$.in
with some configs. I would prefer if the configs are put in tests.sh because it's much easier to manage all test cases there. It already has the hashtag line to separate subtasks, what about putting another line right below for the name (use the default config if empty)?The text was updated successfully, but these errors were encountered: