Can Manual Testing be completely replaced by Automation Testing?

Correct Answer: The differences in responsibilities are listed below: - QA is concern for Process Quality and Programmers are concern for Product Quality - QA ensure that the processes used for developing the product of high quality where as programmers used these processes so that end product is of good quality - Processes are decided by QA Programmers are supposed to follow the processes so that they can produce a good quality product - Any issue found during execution of process by the programmers is communicated to the QA so that they can improve the process

Correct Answer: The main attributes are discussed below: Maintainability: For each new release need to update the test automation suites Reliability: Accuracy and repeatability of the test automation Flexibility: Ease of working with all the different kinds of automation test ware Efficiency: Total cost related to the effort needed for the automation Portability: Ability of the automated test to run on different environments Robustness: Effectiveness of automation on an unstable or rapidly changing system Usability: Extent to which automation can be used by different types of user

Correct Answer: First thing testers are not responsible for fixing the bug they are only responsible for debugging the bug and prioritizing those bugs These bugs are now reported in bug report template with the severity and priority of the bug Tester assigns severity level to the defects depending upon their impact on other parts of application Every bug has its severity and priority values assign by tester If a defect does not allow you to go ahead and test the product, it is critical one so it has to be fixed as soon as possible We have 5 levels as: Critical High Medium Low Cosmetic

Correct Answer: Time Estimation method for Testing Process: Step 1 : count number of use cases (NUC) of system Step 2 : Set Avg Time Test Cases(ATTC) as per test plan Step 3 : Estimate total number of test cases (NTC) Total number of test cases = Number of Use Cases X Avg Test Cases per a use case Step 4 : Set Avg Execution Time (AET) per a test case Step 5 : Calculate Total Execution Time (TET) TET = Total number of test cases * AET Step 6 : Calculate Test Case Creation Time (TCCT) usually we will take 15 times of TET as TCCT TCCT = 15 * TET Step 7 : Time for Re-Test Case Execution (RTCE) this is for retesting usually we take 05 times of TET RTCE = 05 * TET Step 8 : Set Report generation Time (RGT usually we take 02 times of TET RGT = 02 * TET Step 9 : Set Test Environment Setup Time (TEST) it also depends on test plan Step 10 : Total Estimation time = TET + TCCT+ RTCE + RGT + TEST + some buffer

Correct Answer: Use Case: A use case is a description of the process which is performed by the end user for a particular task Use case contains a sequence of step which is performed by the end user to complete a specific task or a step by step process that describe how the application and end user interact with each other Use case is written by the user point of view Use case Testing: the use case testing uses this use case to evaluate the application So that, the tester can examines all the functionalities of the application Use case testing cover whole application, tester performs this testing in step by step process to complete one task

Correct Answer: Regression Testing: When changes in the code of the software are made to fix the previous bug Then testing needs to be perform to ensure that it will not generate a new bug in the application and it works as specified and that it has not negatively impacted any functionality that it offered previously Regression Testing is important because of following reason: - That the application works even after the alteration in the code were made - The original functionality continues to work as specified even after doing changes in the software application - The alteration to the software application has not introduced any new bugs

Correct Answer: Exploratory testing: means testing an application without a test plan and test script In exploring testing test explore the application on the basis on his knowledge The tester has no knowledge about the application previously He explores the application like an end user and try to use it While using the application his main motive is to find the bugs which are in the application Specification-driven testing: means to test the functionality of software according to the user requirements In this, tester inputs multiple data and monitors the outputs from, the test object In this testing tester evaluate the showstopper bugs which break the major functionality of the application This type of testing requires test plan and test

Correct Answer: Walkthrogh: Very informal type of review or testing method Done by peers, so its called peer review Inspection: very technical type of review or testing method, done by the highly technically sound people

Correct Answer: Use case is nothing but the functional specification document in which all the customer requirements are documented Test case is a document which tells wat to test, steps to test and expected and actual results

Correct Answer: Basically Load, Stress and Performance Testing are the same However, Load testing is the test to check the users? response time of number of users of any one scenario of the application whereas Performance Testing is the test to check the user response time for multiple scenario of the same application