Hi, guys,

There is nothing test with the command like the git-abort. It is hardly remember any detail of any command when time goes by.

The Only Constant in Life Is Change.

So I think is useful to create the unit test for each command to leave the description how the command has been expected to run. For now, there are 74 commands, that means 74 uts needed. It is a big job. But first, we can find some ways to save life.

At least, three ways to create the unit test I think, the detials as below:

1. Integration tests in Bash
   • It is great and no more side effect, but i did not know the detail how to, so if someone gives a hand about how to, grateful!
2. Integration tests in Python
   • Save life always
3. Integration tests in Node
   • My favourite cause I use it a lot and so many pkgs to support the process

I think we can take a vote here, any new one is welcome!

One more, the github action or Travis or any other?

Reference

• About continuous integration
• CI/CD explained
• pytest