I read a few ISTQB manuals like the ISTQB Foundation Level, Agile Testing, Acceptance Testing, etc. The only manual where I found some kind of useful references was the Certified Tester Advanced Level Test Analyst (CTAL-TA) but it's not nearly enough.
I am looking for references and some critical knowledge on how to write and organize test cases.
I know that test cases should be modular, organized based on features, reusable, etc.
I am in need of sustaining an argument against bad practices but I am having a hard time backing up my arguments.
To me it is kind of common sense but how to point out that the test cases shouldn't be organized by sprints/releases, that even if duplicating and tweaking test cases is easy, in the long run, it's not sustainable (even if that has been happening for quite some time).
I know how to write code and have clean and organized code because best practices are established but when it comes to documentation (test cases/suites), where can I refer to? Is there any official reference besides ISTQB? Something like the Project Management Institute which has very good and detailed material for its topics.
I will be working on plugging a new automation framework to our test repository and I don't want to spend my time cleaning test cases. I still don't have much visibility on how to do it but I want to plug testrail to jenkins and I think a way to do it is to have sections named the same way as methods.