-
How will you do regression testing if you have more number of test cases..more than 1000 or 2000?
srinivasulub1981
- Nov 26th, 2009
HIWe will give the priority against each test case which writing the test cases it can be given by doing the risk analysis and also they can be reviewed by TL and approved.So when ever we have a suffient time then we will execute all test cases if not we will go for the high priority cases.CNU
ranjana.jadhav17
- May 29th, 2009
In this case we should test the functionality, which is very important & customer will use it evry day.? We can skip the testing of little used features.
-
How do you analize requirements?
srinivasulub1981
- Nov 27th, 2009
HIRequirement analysis is a process of reviewing and understanding the clients expectations from the application. It consists of below stages=> Need to fix boundaries for the Reqs: Firs...
vk1978
- Apr 16th, 2009
By reviewing the Requirement Documents and attending team meetings we do analyize the requirements.
-
How do you implement a new testing process in a company
kurtz182
- Dec 13th, 2009
You do it like this:1) Discover a problem or a need for improvement2) Research ways to resolve the problem or satisfy this need3) Learn everything you can about it a) Its benefit to ...
kurtz182
- Dec 12th, 2009
How do you implement a new testing process in a company?You do it like this:1) Discover a problem or a need for improvement2) Research ways to resolve the problem or satisfy this need3)...
-
You have completed a project and the live date is nextday, you got one big problem but that problem can't be resolved in short time and the estimate is 30 days. Waht are your options ..?
kurtz182
- Dec 10th, 2009
Our options depend on the company profitability and customer perception. Options:1) If the functionality is not mission-critical, then release the application with the impaired funct...
srinivasulub1981
- Nov 26th, 2009
HiAs a tester we can find out the issues at any time as no one can give 100% bug free product, but the thing is we must find out the major issues while doing regression testing, alpha or beta testing ...
-
In my interview, they asked the purpose of Test Approach in Test Plan. I have said it describes what are all the testing methods we have to follow on testing the particular application. But the interviewer said my answer was wrong. Can anyone explain?
kurtz182
- Dec 23rd, 2009
A test approach refers to the manner in which testing will be performed throughout software development. Some options include manual, automation (or a combination of both),&n...
srinivasulub1981
- Nov 27th, 2009
HiI feel test approach will def ined in test srategy doc, not in test plan, because of this reason, he said it's a wrong ansCNU
-
Prioritize your Test Cases
Realizing that you cannot test everything, how do you prioritize your test cases?
preetchana
- May 12th, 2010
Test Cases can be prioritized on the basis of following:1. Test the main functionality2. Test the areas with higher risk, that means where Tester feel that the coding is complex, and their is pos...
chitta10
- Mar 24th, 2010
Frist of all we just have to focus on 1. High risk areas.2. The functionality which will access by more users and for repeated time.3. A little bit of look and feel if it is possiable.
-
When the application is ready for testing ?
When the application is ready for testing but there no time as customer needs the application very soon, what is the solution for testing
-
Mis-Communication in Bug
What will you (Tester) do if there is miscommunication in bugs, Every cycle is Ignored from developer side and Re-Opened from tester Side?
Read Best Answer
Editorial / Best Answer
kurtz182- Member Since Nov-2009 | Dec 6th, 2009
In every test cycle, the defect is consistently 'Ignored' by the developer and 'Re-Opened' by the tester. This problem exists due to a miscommunication somewhere. What will you do as a tester to rectify this issue?
1) I would first make sure that I have entered accurate and thorough details in the defect report in order for the developer to reproduce the issue. I would include details about the test environment so the developer can duplicate it. I would also include screen shots to prove the defect does indeed exist.
If the developer 'Ignores' this, then s/he obviously believes there is no defect at all and that the application's functionality is working precisely as it is supposed to.
2) Next, I would cite the requirement in the defect report and describe my interpretation of it. Then I would describe how the existing functionality does not meet the intended requirement.
If the developer 'Ignores' this as well, then I begin to consider whether I have misinterpreted the requirement. It is possible that the developer is correct.
3) I would revisit and study the requirement to determine whether I misunderstood it when creating my test case(s). If necessary, I would meet with the Business Analyst to gain further understanding about the requirement. I would discuss my test case and the defect with the Business Analyst to determine whether my understanding and approach is correct.
If my research convinces me that I have fully understood the requirement and that my test case accurately and thoroughly tests it, then I would meet with the developer and discuss the results of my investigation with him/her. I would explain the requirement in the manner intended by the Business Analyst. I would reproducethe issue in an attempt to prove how the defect fails to satisfy the requirement. Hopefully, the developer will be encouraged to fix the defect.
If the developer continues to 'Ignore' this issue, then I will get the Business Analyst involved.
4) I would set up a meeting with the developer, Business Analyst, and myself in attendance. I would encourage the Business Analyst to explain the requirement to the developer and explain how the test case and its results properly exercise the requirement and identify a failure.
If the developer still 'ignores' this issue, perhaps it is time to replace the developer!
venkatesh.thangaraj
- Sep 14th, 2010
To be very simple, tester should specify the functional document(FD) which tells the exact functionaly of the piece of code and explains how it deviate from the requirement which lead to a creation of...
folasade
- Feb 18th, 2010
If a developer is fixing bugs with their own ideas and schedule in mind that means he is not following the test cases, he changing the status to IGNORED, then it is an error on the part of the develop...
-
How do you analize severity and priority?
srinivasulub1981
- Nov 27th, 2009
Hi As a tester we need to analize the severity, it's a level of impact on the application as how bad the bug is.In other hand, priority is analysed by test lead or dev lead, it's a level of schedule..CNU
mathan_vel
- Apr 11th, 2009
Its depends on the bug found.The Severity Level is fixed by the Tester and the Priority Level to fix the bug is fixed byt the Developer.How to Analyze? It is simple that how harm the bug is.. what the...
-
Suppose a website contains 20 pages & having similar type of error in most pages.Tester checked one page & posted the bug in a bugtracking system including that this bug remains in most pages but developer only debugged one page (the location Tester had written). Now who is responsible to check other pages Developer or Tester ?
kurtz182
- Dec 10th, 2009
If the tester knew the defects existed on other pages and that a fix on the reported page would not fix corresponding defects on the other pages, then what we have here is a problem in the test proces...
srinivasulub1981
- Nov 26th, 2009
HIIf tester founds an issue and it's exists in remaining 19 pages, it's not required to log total 20 issues, we can log it as one issue and will mention that the issue was exists in remaining ...
-
-
Given time is short and u have to test and release application,what approach u follow to test?
mithr17
- Nov 18th, 2011
Instead of creating test cases for each and every requirement, I would create test scenarios that cover multiple features and modules. This way Im thinking in the feet of an end-user and finding ri...
dadwalm
- May 24th, 2010
I would suggest performing Risk Based testing. Identifying the requirements which if not implemented or wrongly implemented could result into a disaster, prioritize such requirements with the help of ...
-
A system that has been working fine for the past 25 years has been given to you for testing and that has no errors how will you convince your senior that you have performed testing?
kurtz182
- Nov 24th, 2009
The answer depends on how well the senior member knows me. If I have proven my trustworthiness to this senior member in the past, then I simply submit thorough test results and call it...
-
What is dfference between positive and testing testing.which one do you prefer as tester and why?
kurtz182
- Dec 18th, 2009
The difference between postive and negative testing is this:Positive testing attempts to verify that an application behaves as intended (satisfies requirements).Negative testing attempts to revea...
srinivasulub1981
- May 23rd, 2009
Positive Testing : Testing the application with valid dataNegative testing: Testing the application with invalid data
-
You have tested the application and it is released. The user asks for some changes in the project and gives one week time to complete it. Out of the one week, 6 days is taken by the developer to make the changes. So you have only one day to test it. What will you do in the case in case of manual testing?
naresh
- Jul 18th, 2011
What the TL/Manager do till the sixth day, they will track the status of the new requirement every day, they will be knowing the status they should be more aggressive in taking decision in such cases,...
Mr.Maduraikaran
- Jun 16th, 2011
Hi Sailaja, I agree that we can complete the testing in just one day. But what if the condition is like this: You are testing on the seventh day by end of the day, you found a bug. Now the developer f...
-
In my interview...I was asked this question - "who fixes the bug finally..the developer or the tester"...my reply was "developer" which he said was wrong. he said it was the tester..could you please explain ur comments??
Mr.Maduraikaran
- Jun 15th, 2011
Your question is bit wrong.The question should be who closes the bug finally.. the developer or the tester.Always the develper will fix(Modifies the code-the scripting part), and tester will close it (if the functionality is recovered).-Mr.Maduraikaran (The K).
kurtz182
- Dec 23rd, 2009
It is quite possible that the interviewer knew the correct answer but responded the way he did in order to learn a few things about you: 1) How well do you know the answer to the question?&...
-
-
Testing Discussion Interview Questions
Read Best Answer
Ans