![]() ![]() If it's a bug that you're not really worried about having regressions for, maybe you only need to do informal testing, and not embed the test in a formal suite that you run repeatedly. If the only requirement for your testing is that you gain some confidence in your bug fix, then it's really up to you how you gain that confidence. ![]() After all, good testing isn't about checking a box, it's about finding problems! I can add more detail if you're in that situation but it's not as common.īeyond whatever the external requirements imposed by your context, there is the question of what provides value to you and your company. This may not, however, have to be in the form of a test case in a test suite. If you're in a regulated industry, for example, you would be required to keep a lot more documentation around the testing you perform than if you're a startup building todo apps.Įven in regulated scenarios, doing unstructured testing outside the context of your formal testing is likely acceptable and even encouraged, but you may also need to provide some form of objective evidence of the testing performed. Generally what you "should" do is highly dependent on your context. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |