Bugs and Testing

Question 1

What is Software Quality Assurance?

Answer 1

Software quality is a perceptual and conditional thing. It may be understood differently. For consumers and some positions within the software company (upper management, sales, PR, marketing) it is about customer satisfaction. From a QA standpoint, it is about software being up to requirements.
Software QA is the process of monitoring and improving all activities associated with software development, from requirements gathering, design and reviews to coding, testing, and implementation.

Question 2

What is software testing?

Answer 2

Software testing is a process of executing a program or application with the intent of finding software bugs.
It can also be stated as the process of validating and verifying that a software program or application or product:

Meets the business and technical requirements that guided its design and development;
Works as expected;
Can be implemented with the same characteristic;

Question 3

What is the difference between Software Testing and Software QA?

Answer 3

Testing is mainly an ‘error detection’ process focusing on improving the source code.
Software QA is ‘preventative’. It aims to ensure quality in the methods & processes at all the stages of SDLC. (“Quality Assurance” measures the quality of processes used to create a quality product).

Question 4

Why software quality is not perfect?

Answer 4

You can’t find all bugs in software;
Not all bugs which were found will be fixed;
To make perfect software takes a long time but in reality, we have not enough time to fix all bugs;

Question 5

What is adhoc testing?

Answer 5

AD HOC TESTING is a testing method of software testing without any planning and documentation. The tests are conducted informally and randomly without any formal procedure or expected results.

Question 6

What is a Bug?

Answer 6

A software bug is an error, flaw or fault in a computer program or system that causes it to produce an incorrect or unexpected result, or to behave in unintended ways.

Question 7

Bug report components are?

Answer 7

1. Short summary (Bug Title);
2. Environment;
3. Steps to reproduce;
4. Expected and actual results;
5. Attachments if applicable;

Question 8

What is JQL?

Answer 8

JQL stands for Jira Query Language and is the most powerful and flexible way to search for your issues in Jira. JQL is for everyone: developers, testers, agile project managers and business users.

Question 9

How you can search in Jira?

Answer 9

Using basic and advanced search.

Question 10

What is Confluence? What kind of data you can fund in Confluence?

Answer 10

Confluence is a collaboration wiki tool used to help teams to collaborate and share knowledge efficiently. With confluence, we can capture project requirements, assign tasks to specific users, and manage several calendars at once with the help of Team Calendars add-on. You can also find in Confluence:

Private documentation about your project;

Vocabulary glossary abbreviations;

Environments and any other information about projects etc;

How to install tools;

Contact information of team members;

PTO calendar;

Question 11

What are the most important components of test cases?

Answer 11

• Test case ID (assigned automatically by TC management system)
• The purpose (Title, Description) of the test case
• Instruction on how to get from the application base state to a verifiable application output or expected result
• Expected result

Execution properties:

• Actual Result
• Pass/Fail indicator

Question 12

What is a Check List?

Answer 12

A checklist is a catalog of items/tasks that are recorded for tracking. This list could be either ordered in a sequence or could be haphazard.

It is often referred to as a simplified version of a test case. In some companies, this format is used instead of Test cases to decrease writing maintenance time

Question 13

What is Test Suite?

Answer 13

The test suite is a collection of test cases that are intended to be used to test a software program to show that it has some specified set of behaviors. A test suite often contains detailed instructions or goals for each collection of test cases and information on the system configuration to be used during testing. It can take any of the three states namely Active, In progress and completed.

Question 14

How many test cases you can create if you don’t have requirements?

Answer 14

To begin with, I will try to test it based on common sense. When I believe I am at the stage where I can ask questions, I will go and talk to people — team members first, and then the product manager. Based on the information I collected, I will create a test plan and try to get a second opinion on it, probably by sending my doc to PM and QA manager.

Question 15

How do you write test cases?

Answer 15

1. Freestyle

2. Gherkin style.

Question 16

What is Smoke Testing?

Answer 16

Smoke test (also confidence testing, sanity testing) – superficial build acceptance. Smoke testing refers the first test made after assembly or repairs to the system, to provide some assurance that the system under test will not catastrophically fail.

Smoke test – is light type testing, objective is figure out, to verify that all build works, is a life. When the application was released in testing environment QA team started Smoke test.

Question 17

What is Sanity Check Testing?

Answer 17

The difference between smoke and sanity, at least as I understand it, is that smoke test is a quick test to see that after a build the application is good enough for testing. Then, you do a sanity test which would tell you if a particular functional area is good enough that it actually makes sense to proceed with tests on this area.

Question 18

Why do we need to have ‘Bug Triage’?

Answer 18

Bug triage is a process where each bug is prioritized based on its severity, frequency, risk, etc. Triage term is used in the Software testing / QA to define the severity and priority of new defects.

The goal of Bug Triage is to evaluate, prioritize and assign the resolution of defects. The team needs to validate severities of the defect, make changes as per need, finalize resolution of the defects, and assign resources. Mainly used in agile project management.

Question 19

What are Severity and Priority?

Answer 19

Bug Severity is the degree of impact that a defect has on the system. Bug Priority is the order of severity that has impacted the system. Severity is related to the standards and functionality of the system; Priority is related to scheduling.