Sriharsha

• Dec 4th, 2006

 

HI,

First I request for some time and If I am not able get the time then I do Smoke Testing and then I test the main functionalities of the application and the modules related to that main application. I will skip some tests which have less prioroty. skip checking the screen alignments etc.

According to me I'll follow this Process. Is there any other process to follow Plz let me know.

Sriharsha

jainbrijesh

 Profile Answers by jainbrijesh Questions by jainbrijesh

• Dec 5th, 2006

 

keep stress on functionality testing.

schmoo

• Dec 13th, 2006

 

If you are in a position where you are behind the eight ball, it is really too late to do anything.  The trick to avoiding these situations is to prepare and plan up front before the project begins.

In my world, I test quality systems (Systems which may directly or indirectly harm a person) and I can't skimp or cut tests as suggested by others.  A situation like you just presented results in either we don't make the deadline or we put in massive overtime.

If you are on a team that is constantly missing its scheduling mark, then your team's skills (especially your project manager) really stinks.  I know you can't change who you work with, but you can influence them.  For starters, try to have more milestones in your project.  For example, if your project lead has a 6 month project and only two milestones, it isn't sufficient.  You should have milestones every two weeks.  If you fail to meet your milestone in your first month in the project, you can warn your management/customers 5 months before the deadline that the project has already slipped.  By doing so, you can assign more resources and rectify the situation.

ruchikak

 Profile Answers by ruchikak 

• Dec 14th, 2006

 

First , I will request for some extra resource that can help me in testing because I will never compromise on the quality of my work. If that is not possible then I will request for the deference of the deadline.And if that is also not possible then I will request to release that paticular functionality in some further release.

Thanks

Ruchika

Dileep Kumar.G

• Dec 15th, 2006

 

Hi all,

Generally we don't receive code. Anyway, we do ad-hoc testing for finding blocking issues and to get more and more major functionality issues. We have to do regorous testing on the areas where users interact more. We can ignore P3 issues. Generally, it happens most of the times. Becoz, tester doesn't find sufficient time to complete testing. one more thing is, we can say 100% testing is completed but we can't say 100% bug free product is released. Even though u do 1 yr testing on any project still u can find bugs.

Thank you

jagan

• Dec 28th, 2006

 

Hi,

I suggest this answer would be fine always when you go to interviews.

If you are in a position where you are behind the eight ball, it is really too late to do anything.  The trick to avoiding these situations is to prepare and plan up front before the project begins

 

With Best Wishes,

Jagan

sonuraja

 Profile Answers by sonuraja Questions by sonuraja

• Dec 28th, 2006

 

I agree with Jaganji. You have to plan well ahead.