-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Separate sharness tests for reported bugs and regressions #2774
Comments
I like this idea, we should do this. |
I am adding them with #2773 |
Yeah, but if overtime we create many tests for bugs, the t0500 and t0501test scripts could become very big and messy. We should at least reserve some test numbers for more test scripts of both kind. For example t05XX for offline issues and regressions, and t06XX for online issues and regressions. |
Seems like a smart idea. Let's move them over before there is much of a mess. |
License: MIT Signed-off-by: Jakub Sztandera <kubuxu@protonmail.ch>
License: MIT Signed-off-by: Jakub Sztandera <kubuxu@protonmail.ch>
License: MIT Signed-off-by: Jakub Sztandera <kubuxu@protonmail.ch>
Some of tests fit currently named types but some of the would be too specific or too weird to fit in already named kind. What do you thing about creating two more kinds of tests:
t0500-issues-and-regressions-offline.sh
t0501-issues-and-regressions-online.sh
Where tests would be created by per issues/bug basis and would specify for which issues exactly where they created.
The text was updated successfully, but these errors were encountered: