Answer Posted / saurabh
Iterative testing simply means testing that is repeated, or
iterated, multiple times. Iterative usability testing
matters because the ultimate goal of all usability work is
to improve usability, not to catalog problems. A single
usability test - particularly if no action is taken based
on its findings - can only tell you how successful or
unsuccessful you were in creating ease of use. To improve
upon what you already have, recommendations based on the
usability test's findings must be incorporated into a
revision of the product. Once this has been done, it's
advisable to test the product again to make sure that no
additional usability flaws were incorporated with the fixes
to the previously found glitches. In an ideal world, of
course, this cycle of testing would continue as long as
meaningful recommendations for improvement could be drawn
from the usability test results. In reality, it's best to
define quantifiable goals for your product's usability
before you begin testing, and to continue the cycle of
testing and revising until your usability goals have been
met.
| Is This Answer Correct ? | 0 Yes | 2 No |
Post New Answer View All Answers
If there is non reproducible bug which developer is not ready to agree, how you will convince him.
how deployment phase of SDLC differs in product based and in service based company ?
What are similarities of Agile and Scrum?
What is the Diff between Code Walkthrough & Code Review? What is the diff between walkthrough and inspection? What is meant by GUI Testing?
Can anybody give whole test cases for banking module.it should include from start to end .that will help me more.to do study.it should contain account,deposite,withdraw,fd,atm modules.?please try to give me??
What are differences in testing a client server and a web application?
Q) Create Preffered customer: As a customer when i purchase more than $5000 in goods since my first purchase, I become a preffered customer so that i can receive the benefits associated with that status.
what is the general pattern of explanation of projects in interview, can u ans me plz.......... ex: online banking application
Hi Friends, I have completed 3 rounds of an Interview with HR discussion also and got Offer letter from Cognizant, but after in 30 min they send one more email like Offer is on Hold, and its not valid... Could you please guide me any one , Can i expect Offer again from Cognizant or Can i drop the hopes ?.
plz send the test scenarios and test cases for "user name should contain 4 to 8 chars and they should have only vowels"
Explain Test Plan with example? Explain following in the test plan with examples What is being tested? What are pass/fail criteria? When will each test occur? What Hardware & Software environment is required? What features must be tested? What features will not be tested? What are the responsibilities of individuals & organisation in the project?
I have cleared written test and one Technical round in one company? now i have to face an Client Round through telephony? Any body have faced client round, how will it be , wil they ask technical or is it only formality round? im nervous, plz let me know wat all they may ask? i have this round on monday?
What is the difference between system testing and integration testing?
can anybody send the project you have tested with the clear descriptions,and recent bugs u found in that
how many modules in ur bank project? what functionalities r there?how did u check? could u plz expalin ur banking project?