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

Update the --test option #232

Open
matsduf opened this issue Nov 29, 2021 · 0 comments · Fixed by #333
Open

Update the --test option #232

matsduf opened this issue Nov 29, 2021 · 0 comments · Fixed by #333
Milestone

Comments

@matsduf
Copy link
Contributor

matsduf commented Nov 29, 2021

If only the test cases in a module or a single test case is to be run, then the --test option can be used:

	--test STR...          Specify test to run. Should be either the name
	                       of a module, or the name of a module and the
	                       name of a method in that module separated by a
	                       "/" character (Example: "Basic/basic1"). The
	                       method specified must be one that takes a zone
	                       object as its single argument. This switch can
	                       be repeated.

To run all Basic test cases run zonemaster-cli --test basic, but to test only test case Basic04, then "basic" has to be repeated, zonemaster-cli --test basic/basic04. The module can always be deduced from the test case identifier, and the difference between test case identifier vs. module name can always be deduced from the existence of digits a the end.

This issue suggests that the value of the --test option should also accept the test case identifier only. I.e. all the following three forms:

  • --test basic # test all test cases in the basic module
  • --test basic/basic04 # test Basic04 only
  • --test basic04 # test Basic04 only
@matsduf matsduf added this to the v2022.1 milestone Nov 29, 2021
@matsduf matsduf modified the milestones: v2022.1, v2022.2 May 21, 2022
@matsduf matsduf modified the milestones: v2022.2, v2023.1 Dec 20, 2022
@matsduf matsduf modified the milestones: v2023.1, v2023.2 Jun 26, 2023
@tgreenx tgreenx linked a pull request Sep 7, 2023 that will close this issue
@matsduf matsduf modified the milestones: v2023.2, v2024.1 Mar 19, 2024
@matsduf matsduf modified the milestones: v2024.1, v2024.2 Jul 3, 2024
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

Successfully merging a pull request may close this issue.

1 participant