Answer:- Functional testing covers the following types of validation techniques: • Unit testing • Smoke testing • UAT • Sanity testing • Interface testing • Integration testing • System testing • Regression testing

Answer:- • Functional testing: It is testing the ‘functionality’ of a software or an application under test. It tests the behavior of the software under test. Based on the requirement of the client, a document called a software specification or requirement specification is used as a guide to testing the application. • Non-functional testing: In software terms, when an application works as per the user’s expectation, smoothly and efficiently under any condition, then it is stated as a reliable application. Based on quality, it is very critical to test these parameters. This type of testing is called non-functional testing.

Answer:- Software testing life cycle (STLC) proposes the test execution in a planned and systematic manner. In the STLC model, many activities occur to improve the quality of the product. The STLC model lays down the following steps: 1. Requirement Analysis 2. Test Planning 3. Test Case Development 4. Environment Setup 5. Test Execution 6. Test Cycle Closure

Answer:- Fault is a condition that makes the software fail to execute while performing the considered function.

Answer:- A slip in coding is indicated as an error. The error spotted by a manual tester becomes a defect. The defect which the development team admits is known as a bug. If a built code misses on the requirements, then it is a functional failure.

Answer:- • Severity: It represents the gravity/depth of a bug. It describes the application point of view. • Priority: It specifies which bug should get fixed first. It defines the user’s point of view.

Answer:- The criticality of a bug can be low, medium, or high depending on the context. User interface defects – Low Boundary-related defects – Medium Error handling defects – Medium Calculation defects – High Misinterpreted data – High Hardware failures – High Compatibility issues – High Control flow defects – High Load conditions – High

Answer:- Defect detection percentage (DDP) is a type of testing metric. It indicates the effectiveness of a testing process by measuring the ratio of defects discovered before the release and reported after the release by customers. For example, let’s say, the QA has detected 70 defects during the testing cycle and the customer reported 20 more after the release. Then, DDP would be: 70/(70 + 20) = 72.1%

Answer:- Defect removal efficiency (DRE) is one of the testing metrics. It is an indicator of the efficiency of the development team to fix issues before the release. It gets measured as the ratio of defects fixed to total the number of issues discovered. For example, let’s say, there were 75 defects discovered during the test cycle while 62 of them got fixed by the development team at the time of measurement. The DRE would be 62/75 = 82.6%

Answer:- Defect age is the time elapsed between the day the tester discovered a defect and the day the developer got it fixed. While estimating the age of a defect, consider the following points: • The day of birth of a defect is the day it got assigned and accepted by the development team. • The issues which got dropped are out of the scope. • Age can be both in hours or days. • The end time is the day the defect got verified and closed, not just the day it got fixed by the development team.

Answer:- Automation testing is a process of executing tests automatically. It reduces human intervention to a great extent. We use different test automation tools like QTP, Selenium, and WinRunner. Testing tools help in speeding up the testing tasks. These tools allow you to create test scripts to verify the application automatically and also to generate the test reports.

Answer:- Quality Assurance (QA) refers to the planned and systematic way of monitoring the quality of the process which is followed to produce a quality product. QA tracks the test reports and modifies the process to meet the expectation. Quality Control (QC) is relevant to the quality of the product. QC not only finds the defects but suggests improvements too. Thus, a process that is set by QA is implemented by QC. QC is the responsibility of the testing team. Software testing is the process of ensuring that the product which is developed by developers meets the users’ requirements. The aim of performing testing is to find bugs and make sure that they get fixed. Thus, it helps to maintain the quality of the product to be delivered to the customer.

Answer:- A QA or Test Lead should have the following qualities: 1. Well-versed in software testing processes 2. Ability to accelerate teamwork to increase productivity 3. Improve coordination between QA and Dev engineers 4. Provide ideas to refine QA processes 5. Skill to conduct RCA meetings and draw conclusions 6. Excellent written and interpersonal communication skills 7. Ability to learn fast and to groom the team members

Answer:- Here are some facts about the Silk Test tool: 1. Skill tool is developed for performing regression and functionality testing of an application. 2. It is used when we are testing Window-based, Java, web, and the traditional client/server applications. 3. Silk Test helps in preparing the test plan and managing it to provide direct accessing of the database and validation of the field.