I haven't gotten into CI testing since I work alone on the project but I guess learning them would be great when I work on a project with a team. I'm also looking into automated tests :)
A great place to start in CI testing is to pick up a pipeline such as Travis or CircleCI. It takes a little bit of investment up front, but you save in the long run. Builds can be fired off from commits or branch merges instead of manually handing build and deployment. You can put your testing in a pipeline so your code doesn't deploy if your tests fail. Also DevOps is a great way to differentiate yourself as a developer, so building and managing pipelines see great skills to have
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Initially, I started testing in order to fit in the CI, and make Github commits never break things, even minor, again.
Be aware that there are different types of testing, though; including manual testing.
I haven't gotten into CI testing since I work alone on the project but I guess learning them would be great when I work on a project with a team. I'm also looking into automated tests :)
A great place to start in CI testing is to pick up a pipeline such as Travis or CircleCI. It takes a little bit of investment up front, but you save in the long run. Builds can be fired off from commits or branch merges instead of manually handing build and deployment. You can put your testing in a pipeline so your code doesn't deploy if your tests fail. Also DevOps is a great way to differentiate yourself as a developer, so building and managing pipelines see great skills to have