What is your next step? If the software is so buggy

Replies to This Discussion

Permalink Reply by sbharath1012 on November 17, 2009 at 12:34pm

your question is not clear Mary

You mean to say what if the s/w is buggy and not able to test it or howz it ?

• ▶ Reply

Permalink Reply by sbharath1012 on November 17, 2009 at 1:07pm

Agreed with Mohan

We can also say that smoke testing was not done properly or There is no such testing process.

• ▶ Reply

Permalink Reply by Hakan Simsek on November 17, 2009 at 1:28pm

Hi Marry,

By saying buggy, do you mean software has a lot of bugs but not crashing and running? If so, go on and report all bugs. In this condition I offer you, not to start anymore testing effort until 3/4 of the bugs are fixed. Even if a new release comes with say half of them is fixed, just do a regression and check the fixed bugs only. This will save a lot of time for you. I hope this helps.

Regards,
Hakan

• ▶ Reply

Permalink Reply by Sireesha K on November 17, 2009 at 2:25pm

Hi Mary,

First of all we need to do some smoke testing and be assure that software is stable so that we can continue with further testing.
If the software is so buggy,just report the blocking and major issues.Report them to developers even after you have raised the bugs in some bug tracking tool.Its a good practise.

Just intimate the developers to make a another release with bugs fixed.

I do smoke testing,sanity testing than come to complete testing of the software.This is my approach.I have prepared the documents like that.Which were very impressive to all.Till now no project had such documents in my organization and i was appreciated by the leaders for them in my current project.....


Best Regards,
Sireesha/-

• ▶ Reply

Permalink Reply by Siva Taluru on November 17, 2009 at 2:58pm

First of all we need to do some smoke testing and be assure that software is stable so that we can continue with further testing.

• ▶ Reply

Permalink Reply by Himanshu Patel on November 21, 2009 at 2:23am

You should throw that build back to development team

• ▶ Reply

Permalink Reply by Ravi on November 21, 2009 at 8:33pm

Dear,
As we r very well aware of d fact that each n every project is associated with a TIME & COST.

So if u get a Build which is very buggy just perform (BAT-Build Acceptance Testing/Sanity Testing) over it.If It fails in dat pls discuss it wid ur manager and report all these issues to developers.

As its useless to execute any test cases over it if its fail in BAT.If we do so it will effect the COST and Deadline of Project.

Regards
Ravi

• ▶ Reply