QA theory frenzy

functional testing

100

Testing the smallest piece of code that can be logically isolated in a system is called ...

Unit testing

200

This is a type of software testing in which the different units, modules or components of a software application are tested as a combined entity

integration testing

300

What kinds of testing can be included in system testing?

Black box testing

Smoke testing

Sanity testing

400

Explain the difference between smoke testing and sanity testing

Smoke test is done to make sure that the critical functionalities of the program are working fine, whereas sanity testing is done to check that newly added functionalities, bugs, etc., have been fixed. The software build may be either stable or unstable during smoke testing

non-functional testing

100

This is amethod of testing the functionality of a website, app, or other digital product by observing real users as they attempt to complete tasks on it

Usability testing

200

what types of testing are included in performance testing?

load testing

stress testing

stability testing

300

Explain the difference between load testing and stress testing

Load tests help you understand how a system behaves under an expected load. Stress tests help you understand the upper limits of a system's capacity using a load beyond the expected maximum

SDLC

100

Explain what SDLC is and enumerate its steps

The software development lifecycle is the process that development teams use to design and build high-quality software. The goal of SDLC is to minimize risks through planning so that software meets customer expectations. This methodology has a series of steps that divide the software development process into tasks you can assign, complete, and measure. Steps:

Plan

Design

Implement

Test

Deploy

Maintain

200

Name some existing SDLC models

Waterfall

The waterfall model arranges all the phases sequentially so that each new phase depends on the outcome of the previous phase. Conceptually, the design flows from one phase down to the next, like that of a waterfall.

Agile

The agile model arranges the SDLC phases into several development cycles. The team iterates through the phases rapidly, delivering only small, incremental software changes in each cycle. They continuously evaluate requirements, plans, and results so that they can respond quickly to change.

300

What are the cons of using Agile model?

1. Less predictable. The flexibility at the core of the Agile method also means a much lower degree of predictability. It can be much more difficult to accurately estimate the time necessary or quantify the resources and efforts required to complete a project. Many teams fear this uncertainty, and that fear can lead to frustration and poor decision-making.
2. More time and commitment. Communication and collaboration is great, but that constant interaction takes more time and energy for everyone involved.
3. Greater demands on developers and clients. Commitment from everyone involved is required for Agile Methodology to be effective. Anyone who isn’t on board can negatively impact the quality of a project.
4. Lack of necessary documentation. Because tasks are often completed just in time for development under the Agile Method, documentation tends to be less thorough, which can lead to misunderstanding and difficulties down the road.
5. Projects easily fall off track. The less-structured nature of Agile Methodology means projects can easily go astray or run beyond the original scope of the project.

Severity vs Priority

100

Describe severity

It shows how badly the defect has affected the application’s functionality.

200

Describe priority

It defines the order in which developers will fix defects (because priority describes business importance). Note that the higher the impact of a bug on a business’s bottom line, the higher the priority assigned to it.

300

Give an example of a bug with low severity and high priority

The same page may look different in different browsers, elements may miss places, text wrapping doesn't look good, key buttons are not displayed properly, functionality works, but the user experience is not good.

400

Give an example of a bug with high severity and low priority

Few users are still using the older IE versions like IE8. In the banking application, when accessed in older versions of IE, the page is not loaded completely, and the form fields are overlapped. This makes the accessibility of the website difficult for IE users using the older versions.