• Home
  • kumarsingh Answers

Answered Questions

  • Mar 27 2009
    09:47 AM
    26985
    39

    Functional and Usability Defects
    • girishchandra

    What is meant by functional defects and usability defects in general? Give example.

    Star Read Best Answer

    Editorial / Best Answer

    kurtz182  

    • Member Since Nov-2009 | Dec 14th, 2009

    Functional testing refers to tests that verify a specific action or function of an application. Functional testing is performed by testers. Usability testing is a technique used to evaluate a product by testing it on users.  For example, when a tester finds that a text box is not validating properly, he has discovered a functional defect.  When a user doesn't understand a validation message because it uses technical jargon, this would be considered a usability defect.

    It is a good idea to differentiate where defects originate in order to more practically assess a defect's Severity and Priority and many quality managment systems include a "Where found" field that helps identify the source of a defect as being functional (found by tester) or usability (found by end-user). 

    Some software test teams have extended the definition of usability defect to include any defect that describes a lack of intuitiveness when using an application.   

  • Sep 02 2007
    07:08 AM
    36061
    57

    There are 3 mandatory fields and 3 optional fields :How many possible testcases can be written?
    • venkatesank

    DISHA N/A VIRADIYA

    • Jan 4th, 2023

    I will use Decision Making Table Technique. I will prepares 3 positive and 2 nagative test case. 1) 3 man. 1 opt. 2) 3 man. 2 opt. 3) 3 mad. 3 opt. 4)1 man. 1 opt. 5) 2 man. 2 opt.

    abi

    • Feb 18th, 2019

    Test Scenario is a sets of application flow where we can see all the functionality of application whos works .or steps of test cases which are in accommodation. Test scenario is group of test cases for particular application modules where expected result is not mentioned .

  • Jul 19 2005
    09:52 AM
    3366
    18

    Top Ten Tips for Bug Tracking

    A good tester will always try to reduce the repro steps to the minimal steps to reproduce; this is extremely helpful for the programmer who has to find the bug. Remember that the only person who can close a bug is the person who opened it in the first place. Anyone can resolve it, but only the person who saw the bug can really be sure that what they saw is fixed. There are many ways to resolve a bug....

    kurtz182

    • Dec 30th, 2009

    Top twelve tips for initial bug reporting:1) Ensure you can reproduce the defect before entering defect report2) Ensure there are no duplicates before entering defect report3) Include all relevant det...