-
What is a job of a tester in SDLC?
Read Best Answer
Editorial / Best Answer
ramesh7584- Member Since Mar-2007 | Jul 29th, 2007
Overall Business Requirements Phase:
No Tester is required but User Acceptence Test Cases (UAT) need to be defines by the Customer.
Requirements Analysis Phase:
Tester can go through the requirements document and needs to write System testing test cases
High-Level Designing Phase:
Tester Needs to write Integratiosn test Cases
Low-Level Test Cases:
Component testing Test Cases to be documented
Coding:
Unti Testing ( Done by Developers only)
All the test cases activities starts at the end of that phase
Once the coding has been done.. testing starts in phase wise.ramesh7584
- Jul 29th, 2007
Overall Business Requirements Phase: No Tester is required but User Acceptence Test Cases (UAT) need to be defines by the ...
-
HP Mercury's Quality Center and Performance Center
What is the difference between HP Mercury's Quality Center and Performance Center?
nanubujji
- Dec 6th, 2010
HP quality center is the Enterprise Repository tool where are the functioanal test cases are created and executed. Defects logged. Performance center is Enterprise Performance testing tool where the performance test cases/scripts are created and performance test scenarios are executed.
-
Handle Changes Before Ship Date
How would you deal with changes being made a week or so before the ship date?
Read Best Answer
Editorial / Best Answer
kurtz182- Member Since Nov-2009 | Dec 28th, 2009
I would determine the feasibility of meeting the ship date by evaluating the:
1) necessity of the change; [ why do we need it? ]
2) urgency of the change; [ can we defer it? ]
3) complexity of the change; [ how much time and effort will be required to test it? ]
4) risks involved with not including the change; [ what happens if we don't do it? ]
5) additional resources required to test the change [do I have the resources? ]
Then I would either rally the resources to test the change or I would deliver a (hopefully compelling) case against releasing on the target ship date based on my evaluations.kurtz182
- Dec 28th, 2009
I would determine the feasibility of meeting the ship date by evaluating the:1) necessity of the change; [ why do we need it? ]2) urgency of the change; [ can we defer it? ]3) complexit...
-
What is the difference between DATA VALIDITY and DATA INTEGRITY?
kurtz182
- Nov 17th, 2009
The difference between data validity and data integrity is simply this: Data validity deals with data that is input into a system (ex. a database) while data integrity deals with the maintenance...
irinak
- Apr 26th, 2007
Data IntegrityImportant data stored in the database include the catalog, pricing, shipping tables, tax tables, order database, and customer information. Testing must verify the correctness of the stor...
-
Test Design
What is Test Design? Is it preparing the test documents or is it test identification? If the "Test Design" refers to only test identification and "Test Execution" refers to validation, then where should we fit "test document preparation"
Read Best Answer
Editorial / Best Answer
kurtz182- Member Since Nov-2009 | Dec 30th, 2009
Test Design includes all of the steps leading up to Test Execution. The preparation of test documents and the identification of tests are performed simultaneously. Consequently, test document preparation is included in Test Design.
saritha1406
- Nov 1st, 2010
Test Design is done based on the requirements of the project. The different paths for testing are to be identified first. An end to end checklist has to be prepared covering all the features of t...
kurtz182
- Dec 30th, 2009
Test Design includes all of the steps leading up to Test Execution. The preparation of test documents and the identification of tests are performed simultaneously. Consequently, test document preparation is included in Test Design.
-
Prevent Defects
How can the Testing Organization help prevent defects from occurring?
Read Best Answer
Editorial / Best Answer
kurtz182- Member Since Nov-2009 | Nov 20th, 2009
The earlier QA?gets involved in the?software?development process, and the?greater their presence in this process, the more they will help prevent defects.?
QA can review software design documents (cross-functional peer reviews)?before software engineers begin developing their code.? QA can maintain its presence and continue to offer feedback throughout the development process until the initial release of the program to test.??
QA will not prevent defects from occurring, but can minimize the quantity and severity of defects by:
1) Fully understanding the scope of the software development project,
2) Getting involved at the earliest possible stage in the development cycle,
3) Reviewing the project plan for development and offering feedback, and
4) Maintaining a presence in the development process before the first release to test.kurtz182
- Nov 20th, 2009
The earlier QA?gets involved in the?software?development process, and the?greater their presence in this process, the more they will help prevent defects.? QA can review software design documents...
kurtz182
- Nov 7th, 2009
QA will not prevent defects from occurring, but can minimize the quantity and severity of defects by: 1) Fully understanding the scope of the software development project,2) Getting involve...
-
Testing Effort Estimation
How to estimate testing effort following two cases i.e. 1. If Client having high level requirement only. Ex:100 high level requirement2. If client having prototype of the application only.3. If Client having usecases only.4. If client does have any req or usecases.
Read Best Answer
Editorial / Best Answer
kurtz182- Member Since Nov-2009 | Nov 8th, 2009
I'm not sure I fully understand the question, but I will take a stab at this:
In our group, the testing effort is generally considered to be 30 percent of the total development effort in terms of resources when all of the deliverables are properly and thoroughly provided to the test team. These deliverables include requirements and specifications.
"Requirements" refers to the business requirements of the program
"Specifications" refers to the technical specifications of the program
In our group, it is a bonus if we receive usecases. Typically, this isn't necessary when a complete and thorough listing of requirements have been provided.
1. If the client only has the high level requirements, then it depends on how "high" the requirements truly are. If the requirements are so high that all of the necessary test cases can not be reasonably produced with the information given, then extra effort will be needed to query for more complete requirements. If testers must ask specific questions because details are not fully explained in the requirements, this will necessarily incur an increase in test time and resources.
Likewise, the test team has not been given technical specifications for the program. This will incur even more test time and resources when questions are raised such as, "What is the maximum number of characters users can enter in this text box?" or "Are users required to enter a phone number in any particular format?"
In scenario 1, the testing effort estimation is much greater than 30 percent and its specific value depends on information that has not been divulged.
2. If the client only has a prototype, the test team will make it clear that it can not verify whether the program meets company business needs because there are no requirements. Without requirements, the test team can only ensure that the program is stable and user-friendly. The test team may push back and let project manager/marketing/engineering know that it does not recommend an appreciable amount of test effort be applied to the project until requirements are provided. If the test team is compelled to devote a full test run on the project, then it must be made clear that test will not endorse (sign off) on the project and will have to test the program again when the requirements are furnished to the test team. This being the case, significantly more test time and resources will need to be applied to the project.
As we saw earlier, even more test time and effort will be needed when questions arise due to the lack of technical specifications.
In scenario 2, the testing effort estimation is much greater than 30 percent and its specific value depends on information that has not been divulged.
3. If the client furnishes usecases, and if the usecases were based on business requirements, then test will need to verify whether all of the requirements were covered in the usecases. If not, then more test time and effort will be needed to ask the appropriate questions to fill the gap of missing requirements. If the usecases cover all the requirements, and if we can get project manager/marketing/engineering to confirm and sign off on this, then test can begin authoring test cases based on the use cases.
Yet, as we saw earlier, more test time and effort will be needed when questions arise due to the lack of technical specifications.
In scenario 3, the testing effort estimation is greater than 30 percent but less than scenarios 1 and 2. Still, its specific value depends on information that has not been divulged.
4. If the client provides the requirements and usecases, then we are still missing the technical specifications. Yet, this scenario gets us closest to the test team's resources being 30 percent of total development cost. Nevertheless, it is still over 30 percent.kurtz182
- Nov 8th, 2009
I'm not sure I fully understand the question, but I will take a stab at this:In our group, the testing effort is generally considered to be 30 percent of the total development effort in terms...
rahulskin
- Sep 8th, 2009
You can prepare testing effort estimation based on the following.1) 25 to 30 of the development effort. (Approximate)2) You can do the estimation based on the functionality. 3) The size of the s...
-
SharePoint Application Testing
How the sharepoint application testing will be done, I need detailed analysis how exactly the test team validates the application,what would be the test scenarios,Test coverage points.
if any one has done the SharePoint testing,please provide me the inputs -
Handle Bugs in Live / Production
Suppose a bug has been produced in live for the piece of functionality you have carried out testing. How will you give explanation to PM/Manager?
Read Best Answer
Editorial / Best Answer
kurtz182- Member Since Nov-2009 | Nov 10th, 2009
The question is: Suppose a bug has been produced in live for the piece of functionality you have carried out testing. How will you give explanation to PM/Manager?
This issue can not be considered 'Out of Scope' and there must be a test case for it because it is 'a piece of functionality you have carried out testing'.
In this scenario, the tester will need to research to determine whether the issue was caused by 1) a faulty test case, 2) a difference between Production and Test environments, or 3) by the tester's mistake or lack of follow-through. Whatever the case may be, it is the tester's responsibility to isolate the problem and take steps to correct it. Once this has been accomplished, then the particulars of the issue should be fully disclosed to the appropriate individuals (Project Manager, Test Manager, etc.).
1. Faulty Test Case:
a) Does the test case accurately map to the proper business requirement? If not, then perhaps the business requirement was missed and this becomes the source of the problem.
b) Is the business requirement incorrect? If so, then the requirement needs to be rewritten and new test case(s) produced from this new requirement.
c) Was the test case authored improperly. That is, did the tester misunderstand the business requirement and create an improper test case? If so, then the test case(s) need to be reauthored based on this newly correct understanding.
2. Difference between Production and Test Environment:
Does the defect occur only in the Production environment but not in the Test environment? If so, then this must be made perfectly clear to management. The tester may need to work with other functional groups to figure out how to bring the Test environment in alignment with Production in order to prevent this issue from reoccuring.
3. Tester oversight or lack of follow through. As humans, we sometimes make mistakes. There are situations when the amount of time that a test team is allowed to test becomes constricted and testers feel they must hurry to finish their test runs. In these situations, testers inadvertently miss test steps or even entire test cases. And it is Murphy's Law that the overlooked test case will be the one that could have uncovered a significant defect! If this happens, the tester must own up to the error and inform management. I have made my share of mistakes--we all do. It is best to admit the blunder and take personal measures to ensure it doesn't happen again. The most important aspect of ANY relationship, work or otherwise, is trust. And if you try to cover up your mistakes, you will quickly lose the trust of your managment and cohorts. Honest is truly the best policy in any circumstance!trramai
- Jan 18th, 2010
We will check the compatibility and the environment which they are running the software. If there is the issue of compatibility then fault is not from Tester. We will go in Root Cause of the issue and...
kurtz182
- Nov 10th, 2009
The question is: Suppose a bug has been produced in live for the piece of functionality you have carried out testing. How will you give explanation to PM/Manager? This issue can not ...
-
-
Conflict with Developer
On what issues will a user have conflict with a developer?
Read Best Answer
Editorial / Best Answer
kurtz182- Member Since Nov-2009 | Nov 10th, 2009
Conflicts with developers arise from the lack of patience and empathy; when a tester and developer forget that they are ultimately striving to reach the same goal.
Conflicts generally arise through lack of misunderstanding due to miscommunication. In my organization, this typically occurs when a developer closes a defect stating that it can't be reproduced. If this situation is not handled carefully, it can lead to conflict.
Conflict initiators are:
1) Tester did not provide a clear and/or accurate description of the defect. For example, the tester may report the error name or text and the developer might be looking for an error number.
2) Tester did not provide a thorough description of the defect. For example, tester may not mention that the defect was found in a particular test environment and the developer assumed it was caused in a different one.
3) Developer misinterprets the defect even though it was authored accurately, clearly and thoroughly. Devs aren't perfect. Under time constraints to reach milestones, they sometimes overlook key points in defect reports and end up closing bugs that should get fixed.
Conflict negators are:
1) Establish a standard defect reporting process and get Test and Development to fully understand and adopt it.
2) Empathy: Understand that everyone is under pressure to meet deadlines and we are all on the same team to reach a common goal.
3) Patience: Understand that nobody's perfect.Aadit
- Sep 20th, 2012
Tester - developer conflict occur when developer say "could not see the reported bug". This could happen when Testers test environment differ from developrs or when the bug is not reproducible, occuri...
colliewarrior
- Nov 10th, 2009
The issues have a lot to do with approach and personality. Conflict happens not because you are a tester and he or she is a developer. Conflict happens because of bad communication. Communicatio...
-
What are Entry and Exit criteria in Test Plan?
Shahuraj Patil
- Oct 14th, 2012
Explain quality control and quality assurance and its processes with example?
sankumarsingh
- Apr 16th, 2012
Entry and Exit criteria is completely task dependent. Means, it depends on what task you need to do or you have to perform. In general, entry criteria is a set of conditions that permits a task to p...
-
What is Software Testing Principle?
kurtz182
- Dec 14th, 2009
Besides the more fundamental principles supplied by AN_QA from the syllabus for Certified Tester (which are darn good principles, by the way), many testing principles depend on the software developmen...
kumsan060
- Mar 20th, 2008
Make the software build to look as simple as possible, Reduce maximum restriction for customer to use with complex data transaction in simple manner and easy.Anand
-
Fish Model
What is fish model in detail?
-
-
-
What is traceability matrix??
Read Best Answer
Editorial / Best Answer
Answered by: Sahithi
- Nov 25th, 2005
this matrix defines the mapping between customer requirements and prepared testcases by testengineers.this matrix is requirements traceability matrix or requirements validation matrix.this is used by testing team to verify how far the testcases prepared have covered the requirements of the functionalities to be tested.
Amit
- Aug 28th, 2015
Mapping between test cases or requirement is called traceability matrix.
Bhuvaneshwari K
- Oct 10th, 2014
A traceability matrix is a document, usually in the form of a table, that correlates any two baselined documents that require a many-to-many relationship to determine the completeness of the relations...
-
-
Why did you choose software testing?...
If an interviewer asks me " Why did you choose software testing?..." then what should I answer....
-
Give an example for High severity and Low Priority ?
Read Best Answer
Editorial / Best Answer
AmitHam- Member Since Jan-2006 | Jan 9th, 2006
1]High Severity And Low Priority----If there is an application , if that application crashes after mulple use of any functionality (exa--save Button use 200 times then that application will crash)
Means High Severity because application chrashed but Low Priority because no need to debug right now you can debug it after some days.
2]High Priority And Low Severity---- If any Web site say "Yahoo" now if the logo of site "Yahoo" spell s "Yho" ----Than Priority is high but severity is low.
Because it effect the name of site so important to do quick ---Priority
but it is not going to crash because of spell chage so severity low.
Amit Hambarde
Ajit.Rawat3
- Aug 30th, 2012
-> First of all make the clear understanding of severity and the priority of a bug. Severity:- How badly bug is effecting the functionality of an Application. Priority:- How quick we need to resolve ...
rohan.satpute
- Jul 22nd, 2012
High Severity and Low Priority Bugs
- Issue supposes to be caused for Leap Year or Year end.
Low Severity and High Priority Bugs
- Issue such Spelling mistake on GUI Main Screen
Testing Interview Questions
Sub Category
Questions
Answers
Last Updated
Read Best Answer
Ans