I have 2695 unit tests in current project.

Most of them are useless but you still need to maitain them....

  • 0
    Holy shit! Which language/stack?
  • 12
    No, you don't - you need to remove them if they're useless.

    Treat your test code like your main code. It should be well written, free of duplication and performing to spec. If it's not, you need stories in place to reduce that technical debt.
  • 2
    @AlmondSauce amen Boi preach it πŸ§‘‍πŸŽ€πŸ§‘‍πŸŽ€πŸ§‘‍🎀

    Test code is still code (it's the second word in this sentence!)

    If you don't treat her right, she ain't gonna treat you right either
  • 2
    Useless as in trivial? Don't write tests for trivial code (eg. getter/setters and DTOs).
  • 1
    What is the branch/path coverage?
  • 3
    These tests aren't useless. They tick a box on a checklist deemed very important by some manager.

    But you could make some of them actually do some serious testing to make maintaining the actual product easier.
  • 1
    I'd like to see how you write unit tests in nextjs "the backend + frontend framework" πŸ˜‚πŸ˜‚πŸ˜‚πŸ˜‚πŸ˜‚πŸ˜‚πŸ˜‚πŸ˜‚πŸ˜‚πŸ˜‚πŸ˜‚πŸ˜‚πŸ˜‚πŸ˜‚πŸ˜‚πŸ˜‚πŸ˜‚πŸ˜‚πŸ˜‚πŸ˜‚πŸ˜‚πŸ˜‚πŸ˜‚πŸ˜‚πŸ˜‚πŸ˜‚πŸ˜‚πŸ‘ΉπŸ‘ΉπŸ‘ΉπŸ‘ΉπŸ‘ΊπŸ‘ΊπŸ‘ΊπŸ‘ΊπŸ‘ΊπŸ‘ΊπŸ‘ΊπŸ‘ΊπŸ‘ΊπŸ‘ΊπŸ‘ΊπŸ‘ΊπŸ‘ΊπŸ‘ΊπŸ‘ΊπŸ‘ΊπŸ‘ΊπŸ‘ΊπŸ‘ΊπŸ‘ΊπŸ‘ΊπŸ’©πŸ’©πŸ’©πŸ’©πŸ’©πŸ’©πŸ’©πŸ’©πŸ’©πŸ’©πŸ’©
  • 2
    We're at almost 11,000... CI run takes 2 hours πŸ™ƒ
  • 2
    @alturnativ you are doing it wrong
  • 3
Add Comment