Interested to Buy Any Domain ? << Click Here >> for more details...
What is Retesting
- 16 Answers
- 20803 Views
- RMSI, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / ankur
Testing the application across multiple Releases,to make
sure the bug fixes has been done and it does not have any
impact area.
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / kunal
Retesting Means, Re-run the testcase after fixing the bug in new build.
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / subhashqa
“It is a type of testing in which one will perform a
testing on the some functionality again and again with
multiple sets of values in order to come to a conclusion
whether it is working fine or not.”
1.Re-testing start from first build continues up to the
last build.
2.Regression testing start from second build continuous up
to the last build.
3.During regression testing all re-testing will be
conducted.
4.That is the regions some people never call it as re-
testing and regression testing
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / gaurav
it is re-execution of test on same application ,with multiple test data to validate functionality that is re-testing.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / sagarika
after finishing all testcase with bug report if any changes
occur in testing again v r checking all test cases this is
know as retesting
| Is This Answer Correct ? | 1 Yes | 8 No |
what type of documents needed in every phase of sdlc for SQA?
what are the fields in Bug Report
how will you know whether your reported defect rejected?
Can someone give checklist to test the performance of application. This checklist to be provided in the Test Plan that the following will be tested, e.g. 1. n users will be tested to test the load 2. Per page load time would not be greater than n seconds etc. I want to know the points other than the above stated ones.
Can't we write test plan without any document with us or we definitely require the document for that
Hello friends.. Can anybody here explain me or provides me notes of these topics in detail with interview questions... Topics are:- History of Software Engineering Waterfall Model Prototype Model Spiral Model Software Quality Testing Software Development Life Cycle Software Testing Life Cycle white box testing methodology black box grey box Definition of Quality,Quality Assurance,Quality Control Verification and Validation Static Testing Dynamic Testing only on my gmail mca.rachna21@gmail.com
can you plz tell me the all documents to be completed by a manual tester?
Does any one have Performance test plan and Security test plan? Please help me as i need it ASAP... Thanks in Advance.
After asking the defect life cycle, if you think it is not a valid defect, what you will do, whether you will store in any document for future reviews,if yes, what is that document, where you will save that document? or just reject it and close it?
write test case for ecomerce shopping
An engineering college wants to automate their examination activities to speed up their work and maintain high-end accuracy of information. A brief overview of the proposed system is given below: The proposed examination system is consisting of 8 semesters spread across 9 branches (assume your own branch names) and spans over a period of 4 years. Each student belongs to a branch and must register for a minimum of 6 courses but not exceed 8 courses maximum. The scoring pattern for each course is given as below: Maximum marks for each course: 100 Pass: 35% Distinction: 70% and above First class: =>60% and <70% Second class: >50% and <60% Pass Class: >=35% and <50% The proposed system computes the result and announces the results every semester. The results must be accurate and all examination records will be maintained till the students leave the college. Develop a Test Strategy to test the proposed system. Your Test Strategy must include the following: • Test Plan • Testing Methodology to be followed • Test cases • Test effort estimation • Test Correction Mechanism Note: If you need more information on the requirement specification, you are permitted to assume along the same line but clearly specify the details.
How do we do testing if requirements are not documented properly?
Automation Testing 
