-7

Coworker is working on a spreadsheet that I will start using. He is asking me to test it to see if it's good to go. How to tell coworker to get this thing working before sending to me and that he should test it and make sure it's good instead of me doing it?

Yes I can test as an end user but I don't want to help him test the functionality of the sheet itself or the data (he has access to all the old data to validate it just like me). I believe that's his job but I don't want to be rude.

I will be running this not him but he is in charge of making the sheet.

9
  • 3
    I think some more details would help your question. At this moment it isn't clear why you refuse to do an acceptance test of a tool your are going to use.
    – Helena
    May 14 at 7:58
  • 2
    Okay, let's say they come back and say "I've tested it and it works". What are you going to do now? May 14 at 7:59
  • 4
    How are you going to determine "if it works"? By... errrr.... testing it? May 14 at 8:02
  • 3
    Certainly your definition of "testing" to mean "run on dummy data" is not a universally accepted definition; I regularly test on real data. If you have specifically confirmed with your coworker that is what they mean, please edit that into your question because it significantly changes how people will understand the question. May 14 at 8:07
  • 9
    Have you considered that maybe your coworker already does test, but that he wants you to test too, in case he missed some use case he didn't know about? Or in case there was some misunderstanding somewhere?
    – Purrrple
    May 14 at 9:12

3 Answers 3

13

I don't see a problem here. I test things before giving them to people, but I still ask them to test that it meets all their needs as well to confirm I can stop working on it. I assume your colleague is doing the same.

4

It is always good idea to have a second pair of eyes. In my previous work all reports went through another engineer's eyes and in my current work my manager always go through the software I wrote, not through the code, but they use it and give feedback.

I think you approach this wrong way. You are not doing the work for them, you just give feedback to ensure good quality of work.

3

Yes you should be doing the "final" test.

But interim testing should be down to him to iterate towards a final "user ready" product.

You must log in to answer this question.