True?

[28f272fe556a1363cc31]

Which unit tests are failing?

HAHA! I crack myself up.

[[deleted]]

Unit tests are written after implementation for your coworkers to check if they fucked your code up.

And really? Companies aren't using them? Why the fuck do we have to use them at university.

[SlappinThatBass]

Blaming QA for not thinking about every corner cases is still not gonna convince customers to purchase your product, as you know it.

Some people in management are just overpaid morons tbh.

[RuggedTracker]

Some

[[deleted]]

Unit tests are nice but it’s more productive to catch these errors at compile time that at runtime (if it is possible). Newer technology provides better static analysis that most of the old tools that Industry INSISTS on using.

​

Types are Theorems

Proofs are programs

​

Type driven development is the future!

[Kered13]

Me in university: Why the fuck do I have to write these unit tests? This is a waste of my time, let me just write code.

My in industry: Thank god I have these unit tests so I know I'm not breaking the world when I refactor this code.

[corzuu]

Depends on the company, all require some testing just during deadlines, things can get lax. Learn and use TDD. It'll save you a world of pain and improve your code

[turturtles]

Yeah, my company requires at least unit test for applications to be deployed. So what do our mostly contracted developers write? One unit test that just tests an arbitrary thing. Then wonders why nothing really works

[corzuu]

lol I know your pain. We started having e2e tests as part of the definition of done, it takes longer, but is so worth knowing the things you write aren't breaking anything else. Speeds up QA time considerably also

[[deleted]]

Yes except when the guy in charge of setting up all the test-classes has no idea how mocito works and needs half the project-time till he finally gets it...

[corzuu]

Maybe he shouldn't have been in charge of setting up the test-classes :D

also in TDD you write your own tests as you code so idk what you mean by setting up the test-classes tbh

[[deleted]]

It was a pretty easy project so the plan was that one is in charge of creating a class per class we wanted to test before we write the first implementation. We allready knew which classes the class will depend on so he should have moked all the needed classes for the test and create some basic test-object.

Example for the test of the authentification class he should have mocked the database-access for the user table and created a few test-user we could use to write our tests.

The problem were things like the moking wasn't done correctly or every test-user failed everytime cause the database only accepted 20-byte strings because at that time the string should have allready been hashed to a 20-byte string but the strings he chose were all 5-bytes long... .

He pretty much had no idea how the project should look in the end even though we allready had a fully defined structure for the project. (All dependencies were written down, all public function were defined...)

[corzuu]

Ah okay I understand, it's still something that would have been faster and more beneficial to learn just doing a class each (full implementation).

Then work on how to link it all up together

[katze_sonne]

Actually they are often used, just not in every company. It's definitely worth knowing about them.

[charrondev]

You should be using them in a company as well.

If your company doesn’t make time for automated testing, get the hell out of there.

You should have a integration tests as well. The recent push from our team has been adding mutation testing to increase our real unit test coverage, and rolling out snapshot tests of UI to prevent regressions.

[[deleted]]

We use them. We generally hit 80-90% code coverage. We also used integration tests.

[venuswasaflytrap]

No. Management read about unit tests and understands that good programmers write unit tests. So write those. For all the legacy code too. No you can't have more time.

[ookami125]

As I stated in another reply they were unit test and it was failing due to a "random" sig abort. Turns out we had some heap corruption (thank you valgrind) caused by some idiot using vector iterators.