In my previous post Product moving parts as source for test strategy, I explained how I use Github as a tool that helps me to define what parts of product changed and should be tested in regression test.
Github feature that I use is pull request. It presents in clear manner changed files and what was changed in those files. As I have basic knowledge of moving parts (files) of product web framework (in this case Ruby on Rails), I can direct my regression test to test only parts of application that changed.
Sometimes I found an issue and developer updates pull request. How do I know what changed from original pull request?
I call this micromanaging pull request. I just do locall
and I get the list of files that changed in branch and that represent incremental pull request change.
In order to avoid spending time on massive regression test suites (e.g. breakable UI automation), you can use other automation tools, in smart way. Github, Bitbucket, Gitlab are tools that are very important part of my regression test strategy.