Productivity
I was recently asked how automated tests should be named to reflect they were built using Test Studio. My response, hopefully not too blunt, was “Don’t.” Good naming conventions in software are critical. Code is read, re-read, re-re-read, and re-re-re-read 5,632 times more than it’s edited1. Readability is critical to maintaining and understanding our software. With that in mind, great names for classes, methods, variables, and tests are crucial! We need to ensure we’re able to quickly discern what the system’s behavior is, or what a particular test is covering. Good names are about intent, not implementation...