-
Notifications
You must be signed in to change notification settings - Fork 34
after_merge_steps
When you're adding/modifying methods in ru.mystamps.web.service classes you should also add/update unit tests for this code. However, if you didn't provide unit tests then I'm asking you to create an issue for adding them later.
Follow the recommendations:
- Add title by template:
<ClassName>.<methodName>(): add unit tests - Add labels:
techdebt,area/unit tests - Fill comment by template:
Tech debt for: <commit> (#<issueNumber>)
Hint: for a very trivial methods you can generate unit test by using this Golang code: https://play.golang.org/p/0XwWR5K7w-V
Hint: you can add special comments to a code that will create issue automatically.
When you're adding/modifying application behavior (and especially when it's visible to user) you should also add/update integration tests for this. However, if you didn't provide integration tests then I'm asking you to create an issue for adding them later.
Follow the recommendations:
- Add title by template:
Add integration tests for <short case description> - Add labels:
techdebt,area/integration tests - Describe cases with steps that should be tested
- Append to line to comment:
Tech debt for: <commit> (#<issueNumber>)
Hint: you can add special comments to a code that will create issue automatically.
$ git checkout master
$ git push origin --delete <branchName> # remove remote branch
$ git branch -D <branchName> # remove local branch
$ git remote prune origin # remove local copy of remote origin branch
$ git remote prune upstream # remove local copy of remote upstream branch