> I would like to track what the requirements/specifications are, and how we'll test to make sure they're met Why? Why would you like that? Why you? If it's n

> I would like to track what the requirements/specifications are, and how we'll test to make sure they're met Why? Why would you like that? Why you? If it's not happening, the business doesn't care. Your company is clearly not in a tightly regulated industry. What does the business care about? Better to focus on that instead of struggling to become a QA engineer when the company didn't hire you for that. Generally, if the team wants to start caring about that, agree to: 1. noting whatever needs to be tested in your tracker 2. writing tests for those things alongside the code changes 3. having code reviews include checking that the right tests were added, too 4. bonus points for making sure code coverage never drops (so no new untested code was introduced)