Consider if there is no Test lead, No Test Manager and QA
Manager. If you are the senior test engineer, you are
getting pressure from the client to give the build. But you
see that, there r 5 high and 5 low sevierity bugs. So, what
you will do and how you interact with the client.
Re: Consider if there is no Test lead, No Test Manager and QA
Manager. If you are the senior test engineer, you are
getting pressure from the client to give the build. But you
see that, there r 5 high and 5 low sevierity bugs. So, what
you will do and how you interact with the client.
The best way in this situation is to mention the bugs which
are assosicated with the build in document called "Known
Issues".
--- Reply me if i am wrong..:-)
Re: Consider if there is no Test lead, No Test Manager and QA
Manager. If you are the senior test engineer, you are
getting pressure from the client to give the build. But you
see that, there r 5 high and 5 low sevierity bugs. So, what
you will do and how you interact with the client.
first of all i will try to convince my client by telling
that if this problems are not solved then the software
which is released is of no use so give me some days of
timing so that your software will be bug free then i will
solve hi severity problems first and if there is time then
i will go for low severity problems.
Re: Consider if there is no Test lead, No Test Manager and QA
Manager. If you are the senior test engineer, you are
getting pressure from the client to give the build. But you
see that, there r 5 high and 5 low sevierity bugs. So, what
you will do and how you interact with the client.
Hi
If we are using Test director and the client is accessing it
then he can easily know the bugs(High or Low priority) from
the Test director only.
He will directly ask the developer since tester has nothing
to do with bug fixing.
If the bugs are maintained in Excel sheets(Offline) and
If the client asks for the build better discuss with the
developer and inform their view to the client.
Re: Consider if there is no Test lead, No Test Manager and QA
Manager. If you are the senior test engineer, you are
getting pressure from the client to give the build. But you
see that, there r 5 high and 5 low sevierity bugs. So, what
you will do and how you interact with the client.
Depending upon severity we will decide shall we close the
project or not?If the budgs high severity we donot close
project.IF the bugs are not giving any problems to the
client so we will give it for release
Re: Consider if there is no Test lead, No Test Manager and QA
Manager. If you are the senior test engineer, you are
getting pressure from the client to give the build. But you
see that, there r 5 high and 5 low sevierity bugs. So, what
you will do and how you interact with the client.
First of all this will not happen in the real time
scenario. If we assume that there is no Test lead, No Test
Manager and QA Manager and I am the only Senior Test
Engineer who is going to handle this issue I will proceed
in the following procedure.
1. If the bugs are not found before the client?s
pressure, I will make my team work for overnights and try
to find the bugs and report the same in time so that the
developers will fix it in time and will make the product
release in time.
2. If the development of the product is also with our
company then and if I am the only person to take care of
fixing those bugs, I will follow the same procedure as
in ?1? with the development team. This increases the level
of confidence on us for the client.
3. In both the scenarios I will try to concentrate
more on High Severity bugs compared to Low ones at the same
time I will not leave the Low severity bugs. Because high
severity bugs may be blockers which will allow the
application to work up to the mark when the Client sell his
product to his clients.
Re: Consider if there is no Test lead, No Test Manager and QA
Manager. If you are the senior test engineer, you are
getting pressure from the client to give the build. But you
see that, there r 5 high and 5 low sevierity bugs. So, what
you will do and how you interact with the client.
If you found these bugs and logged them before client's
presure,where we have ample time to discover these bugs.In
this case,there is no problem for testers,but the presure
will be on the developers,if he is not fixing the bugs in
time.(This is applicable ,when the client moniters your
daily status).
If you found these bugs and have not logged them before
client's presure,where we have ample time to discover these
bugs.This is the major issue to make convienience them.You
have to convienience him why you missed out those bugs,when
you have plenty of tile to discover with your proper
workarounds and the analasys.In this case,major problem is
for Testers and the developers are cool.
Re: Consider if there is no Test lead, No Test Manager and QA
Manager. If you are the senior test engineer, you are
getting pressure from the client to give the build. But you
see that, there r 5 high and 5 low sevierity bugs. So, what
you will do and how you interact with the client.
Re: Consider if there is no Test lead, No Test Manager and QA
Manager. If you are the senior test engineer, you are
getting pressure from the client to give the build. But you
see that, there r 5 high and 5 low sevierity bugs. So, what
you will do and how you interact with the client.
If you found these bugs and logged them before client's
presure,where we have ample time to discover these bugs.In
this case,there is no problem for testers,but the presure
will be on the developers,if he is not fixing the bugs in
time.(This is applicable ,when the client moniters your
daily status).
Re: Consider if there is no Test lead, No Test Manager and QA
Manager. If you are the senior test engineer, you are
getting pressure from the client to give the build. But you
see that, there r 5 high and 5 low sevierity bugs. So, what
you will do and how you interact with the client.
The criticality/severity and the impact of the bugs should
be communicated to the Client.
Incase the client agrees to receive the build as it is, the
documented concent should be taken along with the schedule
implications.
No client wants a low quality build-specially if it can
lead to system failure. Convince the client and deliver
correct tomorrow rather than delivering incorrect today-
its a matter of reputation, not time.
Re: Consider if there is no Test lead, No Test Manager and QA
Manager. If you are the senior test engineer, you are
getting pressure from the client to give the build. But you
see that, there r 5 high and 5 low sevierity bugs. So, what
you will do and how you interact with the client.
The criticality/severity and the impact of the bugs should
be communicated to the Client.
Incase the client agrees to receive the build as it is, the
documented concent should be taken along with the
implications.
Else should be informed of schedule slippage.
No client wants a low quality build-specially if it can
lead to system failure. Convince the client and deliver
correct tomorrow rather than delivering incorrect today-
its a matter of reputation, not time.
I want the correct answer for this question, because i read
so many answers from this site which have wrong answers for
this question and so during interviews i only gave wrong
answers. If anyone really knows the right answers only
then answer, Pls give the examples for:
High Priority High severity, HP LS, HS LP, LS LP.
Hi Frds., i am Nithi here.here in my company i am working
in manual testing ie. application testing only front end
not back end like i will enter datas and check whether the
record gets updated r not.
what kind of testig is this? and some people r working on
scripting languages same manual testing
what is the difference between these two testing?
ans please
thanks in advance
along with your userid / name. ThanQ
Site Map
