Forcing a developer to add tests out of scope from the original task to code they don't understand Sonarqube came up with ghost PRs Merge conflict from PR sitting due to sonarqube Code missing tests already scheduled to be removed PR is 1 line too long and fails coverage check counting lines in every PR due to sonarqube associated enum switch statement boilerplate adding lines Legacy Editor PR is deduplicating code Combine boilerplate adding lines to PR Adding bad tests for someone else's code to do the bare minimum for sonarqube Module has less than 70% code coverage Code is in App module switch statement adding lines to PR Sonarqube script crashed on CI Adding tests makes line count go over limit for lines that are untestable Original developer of module long gone Entire PR is #targetEnvironment (simulator) Having to explain the same thing over and over for multiple PRs to get exceptions Legacy code that has crash in Sentry Module is more than 2 years old PR is fixing a bug in someone else's existing untested code Legacy renderer GraphQL Forcing a developer to add tests out of scope from the original task to code they don't understand Sonarqube came up with ghost PRs Merge conflict from PR sitting due to sonarqube Code missing tests already scheduled to be removed PR is 1 line too long and fails coverage check counting lines in every PR due to sonarqube associated enum switch statement boilerplate adding lines Legacy Editor PR is deduplicating code Combine boilerplate adding lines to PR Adding bad tests for someone else's code to do the bare minimum for sonarqube Module has less than 70% code coverage Code is in App module switch statement adding lines to PR Sonarqube script crashed on CI Adding tests makes line count go over limit for lines that are untestable Original developer of module long gone Entire PR is #targetEnvironment (simulator) Having to explain the same thing over and over for multiple PRs to get exceptions Legacy code that has crash in Sentry Module is more than 2 years old PR is fixing a bug in someone else's existing untested code Legacy renderer GraphQL
(Print) Use this randomly generated list as your call list when playing the game. There is no need to say the BINGO column name. Place some kind of mark (like an X, a checkmark, a dot, tally mark, etc) on each cell as you announce it, to keep track. You can also cut out each item, place them in a bag and pull words from the bag.
Forcing a developer to add tests out of scope from the original task to code they don't understand
Sonarqube came up with ghost PRs
Merge conflict from PR sitting due to sonarqube
Code missing tests already scheduled to be removed
PR is 1 line too long and fails coverage check
counting lines in every PR due to sonarqube
associated enum switch statement boilerplate adding lines
Legacy Editor
PR is deduplicating code
Combine boilerplate adding lines to PR
Adding bad tests for someone else's code to do the bare minimum for sonarqube
Module has less than 70% code coverage
Code is in App module
switch statement adding lines to PR
Sonarqube script crashed on CI
Adding tests makes line count go over limit for lines that are untestable
Original developer of module long gone
Entire PR is #targetEnvironment (simulator)
Having to explain the same thing over and over for multiple PRs to get exceptions
Legacy code that has crash in Sentry
Module is more than 2 years old
PR is fixing a bug in someone else's existing untested code
Legacy renderer
GraphQL