• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • paul wheaton
  • Devaka Cooray
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Liutauras Vilda
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
  • Piet Souris
Bartenders:
  • salvin francis
  • Mikalai Zaikin
  • Himai Minh

Testing Question

 
Ranch Hand
Posts: 82
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
A standard microsoft testing question..pretty interesting..
"I am a tester. I am testing a software which needs to be released in 4 hours. I find
a severe bug during testing. I report the bug to the developer and give him the time
limit to solve it. The developer says, he needs 4 hours to fix the bug. Now you are
left with no time to test the software after the bug is fixed. What will you do in this
scenario?"

Your take?
 
Ranch Hand
Posts: 1551
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
This question is bogus.
Testers do not give deadlines to developers.
No developer can buy a coke and block of sugar in four hours, much less go through the release process.
Mr. Interviewer, I am going to report the bug and go back to testing for my last 3 hours 45 minutes.
Do you want to work for a company where they have no concept of reality?
 
Ranch Hand
Posts: 541
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Microsoft do testing
 
Bartender
Posts: 4121
IntelliJ IDE Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
"testing a software which needs to be released in 4 hours."

This is hilarious... if you are testing software only 4 hours before release, there's no reason to test it anyway.
 
Rufus BugleWeed
Ranch Hand
Posts: 1551
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The politically astute tester does not find a bug four hours before release. Doing so associates himself with creating a problem. Tell them that your not testing four hours before release. You're a team player. You're on the phone lining up your very attractive, easy, lonely female friends to come out to the pub after work.
 
Author
Posts: 6055
8
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
These are all great answers! Interviewers love being told, "that will never happen" or "your question is dumb." It shows that you're much smarter than the other person and recognize their stupid questions for what they are.
I think he wants to know whether you would put the deadline or quality as a higher priority and what specific actions you would take (e.g. do you make the decision, do you talk to your boss and other people).
--Mark
 
Ranch Hand
Posts: 451
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The pious answer is 'quality', but the real answer (I think) is to consult upwards and sideways. A team decision on whether the bug is significant enough to delay the release for.
 
Rufus BugleWeed
Ranch Hand
Posts: 1551
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Pardon me sir for interupting, but I have given this a lot of thought. If I raise a red flag now it causes a lot of problems for both you and I. If the water fails to fall at the right time, stock price could be affected, sales could be lost, we could look like we have not been doing our jobs. If we ship today none of these problems occur.
Obviously since the bug was not found until this late date, it is relatively infequently executed branch. There will be other bugs that need to be patched. The fix for this can go out with them.
Right now, everybody on the team has been busting their butt. We need the moral uplift of the release. Next week this is business as usual. Today this is a huge crisis and a lot of stress.
The developer should have caught this.
I met these babes at the pool last week. The one really likes to dance. The can sit at the bar all night. She smokes and does shots of ta-kill-ya like you would not believe.
 
Ranch Hand
Posts: 167
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Rex Rock:
A standard microsoft testing question..pretty interesting..
"I am a tester. I am testing a software which needs to be released in 4 hours. I find
a severe bug during testing. I report the bug to the developer and give him the time
limit to solve it. The developer says, he needs 4 hours to fix the bug. Now you are
left with no time to test the software after the bug is fixed. What will you do in this
scenario?"

Your take?


The smart thing to do is : 2) ignore the bug and 2) create a microsoft patch or "enhancement" in a later update which fixes the bug
 
Ranch Hand
Posts: 1258
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Don't employed folks rate the severity of bugs? If it's not going to impact the software, or at least in such a tiny amount, release the software and issue a patch down the road--maybe. If it's going to send the company into financial ruin, well yeah, you may want to wait to fix it, and probably wait longer than 4 hours.
 
reply
    Bookmark Topic Watch Topic
  • New Topic