I really hate how steep the learning curve is for testing. I've been writing the same test for a week for a 150 line directive, and it's driving me fucking nuts. Nothing makes sense. No one in the office to help me. Only 10% of engineers here write any tests. I don't know what to do. Overnight they made it a rule that if you want to move up to the next level for software engineers, 80% of your code needs to have unit test coverage. It's just bullshit.

Omfg, true. I suppose your team is working with another opinionated testing tool. (Don't make me guess...)

Start using rfp with rxjs and immutable state, then use rxmarbles as the mock instrument. All your tests will be end to end and you'll minimize the test surface while increasing surety.

Mutable spaghetti state ensures you'll be writing a ton of tests with a lot of boilerplate just to ensure mechanical "coverage," without the benefit of e2e connectivity.

Thing is writing code and writing tests go hand in hand. For example in my android apps Ive seen shitty untestable spaghetti code many many times. How can I test something that cant be testable without rewriting major parts of whole application?

Thats the problem when devs write code without any plans to write tests for it in the future.

Either ask someones help or get the fck out of there, otherwise you are just ruining your health for no good reason.

At best you will write tests on mocks that barely interact with actual business logic.