[Atotalnoob]

Thank you for the write up.

That seems like a bad scenario with bad technical management. I am wondering if you have considered not trying to implement unit tests and think about end to end tests. This might be easier for antitesting people to buy into because it’s directly ensuring your end users get the desired outcomes.

It doesn’t matter what bad terrible practices you have inside your library if the output is correct…

If you input 1+1, and it outputs 5, it will be obvious how this can be an issue.

What this will enable you to do is get some quick wins and make refactoring safer.

If management still says no, I see 3 major choices.

1. Quit

2. Write your tests and keep them to yourself

3. Mind control

[shaftway]

We do have an integration test that runs just before releases. I've never seen it fail, even when something was obviously broken, so I question the utility of it. There's a specific person in charge of maintaining it.

I've opted for option 4: continue to write code the way they want it written and keep cashing my paychecks. In the meantime there are tons of other improvements that I'm working on, some of which have a more direct impact on business revenue (which has a direct impact on my personal revenue).

[other_herbert]

As a corollary to 2, management tends to love graphs… whatever your using to build should have a plugin that could show unit test success counts and generate even a simple line graph… that alone might be enough incentive to add more testing

[Atotalnoob]

I wouldn’t use the term “unit test” if they are negative on the concept.

Edit; in fact, don’t say test at all. Talk about verification of the output