1. Difference between Priority & Severity

Priority: Priority is defined as the order in which a defect should be fixed. Higher the priority the sooner the defect should be resolved.

  • High
  • Medium
  • Low

Severity: Severity is defined as the degree of impact that a defect has on the operation of the product

  • Critical
  • Major
  • Moderate
  • Minor
  • Cosmetic

2. Difference between QA and QC

QA is a procedure that focuses on providing assurance that quality requested will be achieved where as QC is a procedure that focuses on fulfilling the quality requested.

QA involves in full software development life cycle where as QC involves in full software testing life cycle.

QA is process oriented and QC is product oriented.

QA is focusing on preventing defect while QC is focusing on identifying and fixing the defect.

QA does not involve executing the program but QC always involves executing the program.

All team members are responsible for QA but Testing team is responsible for QC.

QA e.g. Verification. QC e.g. Validation.

QA is a Preventive technique where as QC is a Corrective technique.

3. Testing Methodology:

A testing methodology is a tool or method used to test an application. 

Testing methodologies are approaches to testing, from unit testing through system testing and beyond.

Waterfall Model-In the waterfall model, software development progress through various phases like Requirements Analysis , Design etc –  sequentially. In this methodology, the testing team proceeds to the next phase only when the previous phase is completed. This methodology is not suitable for projects where the requirements change frequently.

Agile Model-Incremental testing is used in agile development methods and hence, every release of the project is tested thoroughly. This ensures that any bugs in the system are fixed before the next release. It is possible to make changes in the project at any time to comply with the requirements.

V Model-V- model is an extension of the waterfall model. Unlike waterfall model, In V-model, there is a corresponding testing phase for each software development phase. Testing in V-model is done in parallel to SDLC stage.

4. What are the advantages of manual testing?

Some advantages of manual testing are:

a) Manual testing of an application identifies most issues, including the application’s look and feel.

b) Manual testing has a low operational cost.

c) Programming Knowledge is not required.

d) It’s great for testing UI’s

e) No Environment Limitations in manual testing.

5. What are disadvantages of manual testing?

Some disadvantages of manual testing are:

a) You cannot record the manual testing process, so it’s hard to replicate it.

b) The manual tests make load testing and performance testing impractical.

c) Testing with large amount of data is impractical.

d) Using a manual test, it is difficult to identify size differences and color combinations of GUI objects.

e) Regression Manual test cases take a lot of time to complete.

6. What’s the difference between a bug and a defect?

A bug is a fault in the software that’s detected during testing time, while a defect is a variance between expected results and actual results, detected by the developer after the product goes live.

7. What about the difference between an error and a failure?

If a program can’t run or be compiled during development, it’s an error. If an end-user discovers an issue with the software, it’s a failure.

8. Differentiate between bug leakage and bug release

Bug Leakage – When tested software is pushed into the market and the end-user discovers defects, this is known as bug leakage. These are bugs that the testing team overlooked throughout the testing phase.

Bug Release – When a certain version of software is launched into the market with some known bugs that are expected to be fixed in later versions, this is known as a bug release. These are low-priority issues that are highlighted in the release notes when sharing with end-users.

9. What do you mean by Defect Triage?

Defect triage is a procedure in which defects are prioritized depending on a variety of characteristics such as severity, risk, and the amount of time it will take to fix the fault.

The defect triage meeting brings together several stakeholders – the development team, testing team, project manager, BAs, and so on to determine the order in which defects should be fixed.

10. Can automation testing replace manual testing?

No, automation testing cannot fully replace manual testing. Automation testing is designed to supplement manual testing, not replace it. Automation testing can automate repetitive, tedious test cases and make the testing process more efficient. However, it cannot replace manual testing completely, as some tests can only be performed manually. 

For example, exploratory testing, usability testing, and user experience testing are all tasks that require manual testing.

11. How to overcome the challenge of not having input documentation for testing?

Answer: IF the detailed standard documentation like BRD and FSD are unavailable, the tester will have to depend on some point of reference.

  • Screenshots
  • A previous version of the application
  • Wireframes, etc

Another factor that helps immensely, is to talk to the developers or the business analysts (when available) to get a confirmation on our understanding or clarifications in case of doubts.

When none of these situations works, we can just conceptualize the application based on our previous IT application experience and create the basic set of test scripts. When the testing phase comes up, we can set up a portion of test cycle time and do some test case management (make the already created scripts perfect) so we have the doc for the next phases.

12. What are the test artifacts involved in QA?

The test artifacts involved in QA are :

Test Strategy, Test Plan, Test Scenarios, Test Cases, Test Summary Report, Bug Report etc.,

13. How do you decide when to stop testing?
There are many factors involved in the real time projects to decide when to stop testing.

  • if we reach Testing deadlines or release deadlines
  • By reaching the decided pass percentage of test cases
  • if the risk in the project is under the acceptable limit
  • if All the high priority bugs and blockers are fixed
  • if we met the acceptance criteria

14. What is the difference between build and release?

Build: A build is a version of a software. Every build has a number for identification purpose. Build is a pre-release version of a Release. Build is given to testing team by developers to test the application locally. Build numbers are incremental.

Release: A release is the distribution of the final version of an application to the customer by a software development team.

15. What is MR and ER?

MR: MR stands for Modification Request. It is used to change the existing functionality in a software, it is usually requested by clients.

ER: ER stands for Enhancement report. It is used to add a new feature in a software. It is usually requested by clients.

16. What is Cross browser testing?

Cross Browser Testing is a type of non-functional test which helps us ensure that our website or web application works as expected in various web browsers. We could do Cross Browser Testing on different browsers both manual and automated way.

To do Cross Browser Testing manually, we (Software Testers) create tests for each browser and execute it manually on each browser. Every browser displays a website in their own style. We usually cannot have all the browsers on one machine. Each browser is designed by a different vendor. So each browser has their own features to showcase their unique presence.

While testing a website, we need to ensure that our website is appearing same across all the browsers. To do this we need to have all the browsers. Fortunately, there are some tools to perform cross-browser testing without testing individually in a manual way.

17. What is the difference between Compatibility testing and Cross browser testing?

Compatibility testing: Testing an application on different hardware or software platform is Compatibility testing.
Example: Different devices such as iPhone, Samsung etc., Different operating system such as Windows, Linux etc.,

Cross browser testing: Testing a web application on different browsers is Cross browser testing. Cross browser testing is a subset of Compatibility testing.
Example: Google Chrome, IE 10, IE 11, Firefox 43 etc.,

18. What are the various tools you have used in testing process?

The tools which I have used during testing process are as follows.

Test Management Tools: JIRA, TestLodge, Quality Center
Test Case Management Tools: TestCaseLab
Defect Tracking Tools: Bugzilla, MantisBT, Jira
Automation Tools: QTP/UFT, Selenium, LoadRunner
GUI Tools: Froglogic Squish
Cross Browser Testing Tools: CrossBrowserTesting, BrowserStack

19. What do you mean by defect detection percentage in software testing?

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%

20. What is meant by latent defect?

A latent defect is a hidden defect in an application/software, which cannot be identified by a user. However, this will not cause any failure to the application because the conditions will never be met.

**Full blog will be updated shortly**