Test automation tool to assist running something, and checking something, then reporting something; when you commit something.
Test automation tool to assist running something, and checking something, then reporting something; when you commit something.
, thank you.After entering the following command:
git commit -m 'latest changes' <COMMIT_FILE_NAME>
Git runs any Git hooks found in \
pre-commit creates a file (${REPOSITORY-NAME}/hooks/COMMIT_FILE_LIST) which includes file(s) that are commited.
post-commit searches for a TEST/\
Why did I create git-TEST-commit-automation when there are so many great open software and enterprise level testing solutions available. I needed something that would
TL;DR - During code design, a software developer’s focus is on how to solve parts of a bigger solution. A developer may throw out a couple to dozens of lines of code. It did not matter that those lines of code did or didn’t meet every test requirement. As a design matures it is increasingly important to have code PASS tests. It is also important for a developer to design SA and FVT test cases for their new code. At that time their code is ready for additional testing using open software and enterprise level testing solutions.
Funciotnal Verification Test (FVT) is defined as the process of verifying that the design meets its specification from a functional perspective. … Functional verification establishes that the design under test (DUT) implements the functionality of the specification correctly.
Static Analysis (SA) is the examination of code prior to the program’s execution SA is code analysis, syntax, permission, code inspection, code review, etc.
pre-commit
post-commit
. . . some methed will notify someone of the results. (not sure which method is going to work for me and you?. . . stdout, logs-scrape, tables, email, twitter, slack, call a friand, etc.)
git-set-env-for-manual-test.sh
git-setup-TEST-cases.sh
git-TEST-cases.sh
git-uninstall-TEST-cases.sh
/usr/local/bin/ <-- <BIN_DIR>├── git-set-env-for-manual-test.sh├── git-setup-TEST-cases.sh├── git-TEST-cases.sh└── git-uninstall-TEST-cases.sh
hooks directory The \
Place the expected results from the test case into a file with the same test case name but add ‘.expected’ (‘dot’expected). Pipe the output from the test case into a file with the same name but add ‘.test-case-output’.
WARNING: These instructions are incomplete. Consider them as notes quickly drafted on a napkin rather than proper documentation!
Quick test case branch merge from test team’s custom test cases without merge conflicts (include steps)
git remote --verbosegit remote add origin https://github.com/BradleyA/git-TEST-commit.gitgit remote --verbosegit push -u origin mastergit-TEST-cases.sh -c --hooksgit branch -agit branch git-TEST-commit-#1git push origin git-TEST-commit-#1git branch -a# create a branchgit pull # get latest pushed commitsgit checkout -b development # create development branchgit push --set-upstream origin development # create github development branch upstream (github)# orgit push -u origin development# write code in development branch# create README on github master branchgit pull origin master # pull chnages to master bransh to development bransh# write code in development branch
Please do contribute! Issues, comments, and pull requests are welcome. Thank you for your help improving software.
@bradleyaustintx" alt="Follow @bradleyaustintx" /> 
MIT License
Copyright (c) 2020 Bradley Allen
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
