What is the difference between error, defect,fault, failure and mistake
Error (mistake) A human action that produces an incorrect result. Defect (bug, fault) A flaw in a component or system that can cause the component or system to fail to perform its required function, e...
Error:it is at the developers end when an application fails to run.
Defect:Same problem when occurs at the testers end,it is named as Defect.
Failure:Same problem occurs at the end users application.
Give an example for high severity and low priority ?
Answered by: AmitHam
View all questions by AmitHam View all answers by AmitHam
Member Since Jan-2006 | Answered On : 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
-> 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 ...
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
Answered by: srinivasulub1981
View all questions by srinivasulub1981 View all answers by srinivasulub1981
Member Since Dec-2005 | Answered On : May 28th, 2009
HI
There is no tool to calculate the estimates, it can be give depends on exp only or else by doing some metrics we can do it.
And Microsoft Project Plan is not for calculating the time, it's just for scheduling the tasks once estimations were given.
CNU
one word - NO!
Best and common practice is to look at past data from similar projects and bump up the time by 25-30%.
Project Management Tool doesn't calculate the ratio, you will be deriving the ratio based on the inputs you provide. There are scenarios where in you require more time for testing than development (c...
It depends upon following Factors:
1. Type of Project/Delieverable.
2. Scope of Testing.
3. Types of Testing to be Performed.
Testing can vary for 30%-50% of total Development Time. I have considered the case of Manual Tesing here. Automation can reduce the end delieverable timelines.
The answer to this question depends on the industry, software development model, company, and project. In my company and on most my projects, we allocate roughly 35 percent of total development resources on our test effort.
Best to solve defects - requirements, plan, design, code / testing phase?
Answered by: Satya Prakash
Answered On : Oct 4th, 2005In any phase, the sooner we see a defect, the less is the cost spent on rectifying the defect. It becomes a costlier affair in later stages. The best phase is Requirements phase. When the defect is found in later phases, it costs more for its correction.
As we are aware, in SDLC later the defects identified, costlier is the Project Delieverable. Earlier the defect identified & resolved, cheaper is the costing. So, as per the provided option, Best time to resolve the defects is during the Requirement Phase.
The Best time to solve defect is at the requirement Phase - by business Analyst, plan, design - for developer using static analysis tools and testing phase by testers. Defects find at the in...
Define quality - bug free, functionality working or both?
Quality of the software is what the client pays for. It means it should perform the intended functions without any major flaws.
Quality Software Deliverable means:
1. Delieverable meets User/Customer Requirements.
2. Reasonably Bug-Free Software.
3. Delivered within defined Timeline & Budget.
4. Easily Maintainable. Also, Less Post Release Maintainence Activity, thus reducing Cost.
Answered by: Satya Prakash Itharaj.
Answered On : Oct 4th, 2005The main purpose of Software testing, I think is not to remove the bug but to find the bug. Also ensuring the application works correctly as per the requirements and thereby increasing the quality of the product and increasing the confidence in the product.
Its Quality. Testing is a Quality Control (QC) activity. Software testing is the process of finding the defects so as to improve the quality of software. It doesnt mean that the software is 100% defect free but the quality will be high after validating when compared before testing.
Purpose for Software Testing:1. To ensure whether the software Build is as per User Requirements/.2. To ensure reasonably Bug free Software, to uncover bugs withing software, if any.3. To improve qual...
4 Types of Testcases should be automated:1. Testcases which has high path frequency i.e. Testcases which are executed with high degree of frequency in production enviroment should be automated.2. Test...