File tree Expand file tree Collapse file tree 3 files changed +49
-0
lines changed
Expand file tree Collapse file tree 3 files changed +49
-0
lines changed Original file line number Diff line number Diff line change 1+ ### Prerequisites
2+
3+ * [ ] Can you reproduce the problem in safe mode?
4+ * [ ] Are you running the latest version?
5+ * [ ] Are you reporting to the correct repository?
6+ * [ ] Did you perform a cursory search?
7+
8+ ### Description
9+
10+ [ Description of the bug or feature]
11+
12+ ### Steps to Reproduce
13+
14+ 1 . [ First Step]
15+ 2 . [ Second Step]
16+ 3 . [ and so on...]
17+
18+ ** Expected behavior:** [ What you expected to happen]
19+
20+ ** Actual behavior:** [ What actually happened]
21+
22+ ### Specifications
23+
24+ - Version:
25+ - Platform:
26+ - Subsystem:
27+
28+ You can get the version information from executing ` commander --version ` .
Original file line number Diff line number Diff line change 1+ Fixes #
2+
3+ ## Checklist
4+
5+ - [ ] Added unit / integration tests for windows, macOS and Linux?
6+ - [ ] Added a changelog entry in [ CHANGELOG.md] ( ../CHANGELOG.md ) ?
7+ - [ ] Updated the documentation ([ README.md] ( ../README.md ) , [ docs] ( ../docs ) )?
8+ - [ ] Does your change work on ` Linux ` , ` Windows ` and ` macOS ` ?
Original file line number Diff line number Diff line change 1+ # Development documentation
2+
3+ ## Writing integration tests
4+
5+ Commander tests itself. You can find the integration tests in ` commander_unix.yaml ` and ` commander_windows.yaml ` .
6+ More complex scenarios are stored in ` integration/ ` .
7+
8+ It is always necessary to execute the test suite with a stable version of commander and not the current build.
9+
10+ ** Tipps:**
11+
12+ - The working directory is by default the project root, even for tests located inside ` integration/* `
13+ - Execute ` commander ` inside the ` commander_*.yaml ` files with a given suite and assert the result which is returned
You can’t perform that action at this time.
0 commit comments