I am a software tester, working on a project which has multiple different environments:
- dev: developers are doing work here. This code is known to be under development.
- test: this code has been released by the developers, and is expected to be ready to test
- prod: this code has been released by the testers, and is expected to be ready for use by customers
The question is: as a tester, should I be looking at / testing the 'dev' version of the product?
On the one hand, I can see this being helpful, in that if the developers are doing something wrong, or have misinterpreted a requirement, I might be able to catch it earlier in the development process, when it would be easier to fix the problem with less effort.
On the other hand, I can see this being harmful, in that I am looking at the product in a state when it is known not to be ready for me. I could end up filing bug tickets on something which the developers already know is an issue, and intended to fix before releasing it to me. This could both result in my filing more bug tickets than necessary, and causing slowdowns or errors by the developers by unnecessarily redirecting their efforts, or otherwise interfering with their process.
So I am conflicted as to whether doing this is good or not. If anyone has any experience with having done this in the past, I'd appreciate your input on whether it ended up being a net negative, net positive, or if there are any things to watch out for when doing so.