4
Creep
12d

I can't fucking focus on writing test cases. Dis shit boring. Entertain me.

Comments
  • 2
    What helps me writing testcases is the thought having a lot of useful tests and confidence in my own code
  • 5
    If you can't think of testcases, you might want to split up functionality, so that you are able to think about testcases more easily.

    Writing testcases can be fun! Or well... it's just my mindset which focuses on destruction :D
  • 3
    How about trying to write test cases you expect to fail? Think like a QA engineer would.

    "What's a way of using this that I haven't thought of? Can I test that?"
  • 1
    @alexbrooklyn The problem with writing test cases after you've written good code is that you've likely already informally tested all of the test cases.

    This makes writing test cases good for detecting changes to the code which may impact functionality but not necessarily code quality in the first place.

    Asking a developer to write their own test cases is like asking a restaurant to write their own reviews.
  • 0
    @JustThat Exactly. I'm testing an internally used tool I created that exports test results as excel spreadsheet. You can't fuck anything up as a user, you basically pick the test you want to export from a dropdownlist and click the button. That's it. And I know that the calculated values inside the spreadsheet are correct since I already checked the integrity of the them while writing this tool.
  • 0
    @Creep Time to think outside the box.

    "How can this be misused?"

    or

    "What is another way to use this that someone may try?"
  • 1
    What the fuck is tests though
  • 1
    @Pogromist exams and assignments
Add Comment