31

Software tester here. Developers what do you think about us honestly? Do you enjoy testers who point out bugs directly or are we a pain in the ass? I feel like developers appreciate my work. I can ask them questions and they are happy I can point out flaws in the app directly. It's also fun to do as a temporary job now.

Comments
  • 15
    I'm glad you exist since I don't enjoy testing at all. You guys aren't a pain the ass, testing is.
  • 23
    I like it if your bug reports contain steps to reproduce.
  • 4
    Like @creep said, I'm happy to have you guys in our team

    Testing is an art and I can't seem to grasp it
  • 4
    @kescherRant Always! ;p I got a template in the beginning of the job for jira tickets and it is obligated :)
  • 2
    @Creep Yea sometimes the manual testing can get boring. But I love how I point out a bug and next build it is fixed. So I do add some value to the project then.
  • 2
    @thatguyatwork Yeah of course you add a great value to the project. It's just nothing for me personally
  • 10
    I'll answer this one as directly as possible, it's not speaking directly to you, just my experience.

    I don't respect testers unless they automate a large portion of what they're testing and follow a rigorous process. Testing *should* go like this:

    0. Run the entire test plan, start to finish
    { for all tests that fail:
    1. Identify bug
    2. validate it is actually a bug (counter to documented expectation/acceptance criteria, anything else is a change request)
    3. document repro steps, notate descendant tests
    4. create an integration test to that will automatically run the documented steps, test output
    5. publish that test to the master testing suite
    6. file a ticket to resolve the bug, submit for grooming
    }
    Ω. goto 0

    If it's anything outside of a process that resembles that, it's providing negligible value.

    A tester should also know the difference between a bug and their personal preference. If you want devs to hate you, suggest changes to the design and/or create tickets to do so.
  • 5
    I appreciate the time and effort testers put in to validate something has been built to expectations, and finding any side cases that could create a problem I've missed.

    But I can understand how a dev may be inclined to hate you if their work is incorrect to begin with and you start calling them out on it, I know that's what your job is, but some devs hate being told their wrong.
    Many a time I've been in the middle of that fight and have to basically explain the ticket in depth and tell the dev to actually test their work before handing it over to testers.
  • 1
    I'm not paranoid, I just don't like testers.
    Don't ask me why... Cus finding bugs on devs code generally is not something to smile about.
  • 5
    I wish we had, like, any. Or automated UI tests. It'd prevent a ton of obvious mistakes from going back through the build train for another week or two.
  • 2
    Never worked in a company that had dedicated testers. I usually rely on myself and some key users for beta testing.
    That being said I would and have always valued the input they had. On a side note I don't like just a "this doesn't work", please tell me where and what steps so I can (hopefully) reproduce it.
  • 4
    I'm glad you're here. While I strive for high-quality software, there'll be things I miss, because to err is human.

    I've been on the other side for a while, too. Clear, minimal steps to reproduce a bug don't just help devs, they help the tester too when it's time to retest a bugfix.

    For automation, devs and testers should work together way more closely. I've been on teams where the devs had a comprehensive UI test suite - and the testers unknowingly had their own almost identical one, written with a different tool. That's wasted work. Use the same automation and share the test cases.
  • 0
    @kescherRant If you don't know how to reproduce by now...you must be in IT. 😆
  • 3
    There have been times where I've wanted to wring your (not you, but the universal tester) neck and tell you "The user isn't going to do that. They aren't going to run this in 3 separate tabs AND use postman to hit the same endpoint, and if they do they deserve the bug", but more often than not, you stop me from putting something really dumb and easy to fix in prod. Well done, and good on you, buddy.
  • 2
    Very very useful.

    Even bug reports that are non-reproducable are helpful to know about.

    And feelings too.

    From, "I feel like its too slow because its trashing the storage." to "That colour scheme freaks me out.."

    I'm pretty good at breaking things myself, but its always helpful to have others do the same thing, since the can break things in ways I hadn't thought of !
  • 2
    better know about bugs before live users complain about them. but the thing is, if u publicly post on whatever platform company members are in about the bugs, thats an asshole move. come to me directly because in some companies the more bugs a dev makes the more they rethink hiring him, use it as an excuse to not give him bonuses, etc... so just keep that in mind i guess
  • 3
    I once worked at a place where we had a dedicated software tester.

    We had the best arguments and learned to love eachother.
  • 2
    I and many people see them as second class developers(right or wrong). I have seen many times that good developers are sent to development team and rejects to test team. When my manager assigned a test taxk, I felt insulted and asked for changing tasks.
  • 2
    @JustThat A software tester is supposed to say how they came to see a bug. If they just say "hey look this bug exists, good luck finding the rare circumstances it happens at", it's much less helpful.
  • 3
    Tester? Hell yeah, i personally (as probably a lot of devs think so) hate testing.
    You guys make our lifes easier, especially if you write steps for reproduction in the bug.

    Thank you for your hard work!!
  • 0
    I generally do. Ours cover multiple products and do support.
    I kind of feel sorry for them. Us devs have no time for tests so you poor sucker's got to check it (we got to check it first) I wish some of the stuff they do can be automated but no time for that. But a lot of time they find inconsistencies and how somewhere way far in the edge of the system is affected by the change, but we iterate so fast automated sections so fast, automated testing would be pointless
    Also steps to reproduce, screenshots, console errors/network are handy
Add Comment