Brainscape's Knowledge GenomeTM


Top Flashcards (Certified)
All Flashcards

QA Methodology > Question and Answers > Flashcards

Question and Answers Flashcards

(115 cards)

Start Studying
1
Q

What is the difference between system software and application software?

A

Software can be system software like your operating system - Windows system. Application software - this power point

Example: Windows is an example of system software, while PowerPoint is an example of application software.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

How many types of application are there?

A

4 types - Desktop, Mobile, Client Server and Web based

Example: Examples of desktop applications include Microsoft Word, mobile applications include Instagram, client-server applications include email clients, and web-based applications include Google Docs.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What are the tiers of web based application?

A

Web tier (GUI), Server tier and Database tier

Example sentence: The web tier handles the user interface of the application.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What is GUI?

A

It is Front End. GUI stands for Graphic User Interface (look and feel)

For example: The GUI of the application includes buttons, menus, and other visual elements.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is Functional testing?

A

Testing functionalities of the application. Testing intended purpose of the feature

Functional testing ensures that the application works as expected based on its specifications.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What is Non-Functional testing?

A

Non-functional is how the functionality should perform, performance of it.

Non-functional testing focuses on aspects like performance, usability, and security of the application.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What is Test Scenario?

A

What QA is trying to validate. Test of the application. For ex: Verify Login functionality

Test scenarios help in defining the steps to validate a specific aspect or feature of the application.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

How many types of Test Scenarios are there?

A

2 Types: Positive and Negative. Positive is simply testing what the functionality is supposed to do. Negative is testing what it is not supposed to do.

Positive test scenarios validate the correct behavior of the application while negative test scenarios focus on error handling and boundary cases.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What is Mobile Application

A

applications that are installed on a phone or tablet

For example this PowerPoint application

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What is Desktop application

A

installed locally and doesn’t require internet connection to run. For example this PowerPoint application

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What is Web based application

A

Application that user accesses thru a browser (Opera, Firefox, Safari, Chrome, Edge, etc)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What is Client Server application

A

application that is installed on a computer and requires internet access to work (Skype)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What is Mobile Application

A

applications that are installed on a phone or tablet

For example this PowerPoint application

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What is Desktop application

A

installed locally and doesn’t require internet connection to run. For example this PowerPoint application

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What is Web based application

A

Application that user accesses thru a browser (Opera, Firefox, Safari, Chrome, Edge, etc)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What is Client Server application

A

application that is installed on a computer and requires internet access to work (Skype)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Who gathers the Requirements?

A

BA (Business Analyst) gathers and writes Requirements Documentations

Example: BA works closely with stakeholders to gather and document the project requirements.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

What are the phases of Waterfall?

A

Requirements Gathering, System Design, Development, Testing, Deployment and Maintanence

Example: The Waterfall model follows a sequential approach with distinct phases for each aspect of the project.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

What documentations are created by BA in Waterfall Methodology?

A

BRD (Business Requirement Documentation), FRD (Functional Requirments Documentation), SRS (System Requirement Specification)

BA is responsible for creating detailed documentation to ensure clear understanding and communication of project requirements.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

What is Test Case?

A

Documentation that outlines step by step guide to test one or more functionality of the applicaiton

Test cases are essential for ensuring the quality and accuracy of the application’s functionality.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

What testing Developers do?

A

Unit Testing

Developers perform unit testing to test individual units or components of the software

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

What testing BA does?

A

UAT (User Acceptance Testing) Testing

Business Analysts are responsible for User Acceptance Testing to ensure the software meets the requirements of the end users

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

What happens in Deployment phase?

A

Application put into Production Environment so that clients can start using it

During the Deployment phase, the application is moved into the production environment for client use

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

What happens in Maintanence Phase of Waterfall?

A

Any new changes are implemented, improving the application or fixing defects

In the Maintenance Phase of the Waterfall model, any necessary changes are made to enhance the application or address defects

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
What testing QA doesn't do?
Unit Testing (QA Never does it), UAT Testing (it is BA's job but QA can help out if need be) ## Footnote Quality Assurance (QA) does not perform Unit Testing or UAT Testing, but they can assist if required
26
What is Smoke/Sanity Testing?
The test that checks whether the application is ready for further major testing and working, without dealing with the finer details. You just go over main purpose of the application. ## Footnote Example sentence: The team conducted smoke testing to ensure the basic functionality of the application was working before moving on to more detailed testing.
27
What is GUI Testing?
Testing what you see on the GUI, buttons, drop downs, color, feel, spelling, functionalities. ## Footnote Example sentence: The QA team focused on GUI testing to ensure the user interface elements were functioning correctly.
28
What is Functionality Testing?
Testing what functionalities supposed to do. ## Footnote
29
What is System Testing?
Testing all the functionalities of the system from A to Z. ## Footnote
30
What is End to End Testing?
Testing the complete path of the functionality, it might involve several systems (upstream and downstream). ## Footnote
31
What is Performance Testing?
Performance Testing is divided into: Load, Stress and Volume Testing ## Footnote Load Testing: Loading the system with many users. Volume Testing: Uploading and downloading huge amount of data Stress Testing: Going beyond the performance limits of the application with users and/or data
32
What is Recovery Testing?
Recovery testing is very necessary to check how fast the system is able to recover against any hardware failure, catastrophic problems or any type of system crash. Usually performed simply unplugging computers from the power source ## Footnote
33
What is Security Testing?
Testing how secure the application is. ## Footnote
34
What is Performance Testing?
Performance Testing is divided into: Load, Stress and Volume Testing ## Footnote Load Testing: Loading the system with many users. Volume Testing: Uploading and downloading huge amount of data Stress Testing: Going beyond the performance limits of the application with users and/or data
35
What is Recovery Testing?
Recovery testing is very necessary to check how fast the system is able to recover against any hardware failure, catastrophic problems or any type of system crash. Usually performed simply unplugging computers from the power source ## Footnote
36
What is Security Testing?
Testing how secure the application is. ## Footnote
37
What is the difference between System vs E2E Testing?
System testing is testing all the functionalities within that system. E2E Testing is on the other hand testing 1 functionality from start till the end. E2E Testing usually involves GUI, Servers and Databases. ## Footnote Example sentence: System testing ensures that all components of the system work together seamlessly.
38
What is the difference between Unit and UAT Testing?
Unit testing is done by Developer. UAT is done by BA. ## Footnote No additional information.
39
What is the difference between Load vs Volume testing?
Volume testing is testing with huge data, upload or download data to the application. Load is usually performed by loading the system with many users simultaneously to check if the application works during the peak hours. ## Footnote No additional information.
40
What is Epic?
Epic is a big sellable idea for mostly management. You rarely get Epic at work. Epic is broken down to one or more user stories. ## Footnote Epic is a high-level summary of a large feature or project that provides value to the business.
41
What is a User Story?
User Story is a simple goal, not a sequence of actions. ## Footnote User Story is a brief description of a feature told from the perspective of the end user.
42
What is a Use Case?
Use Case is detailed steps of user action and system response. Can cover one or more User Stories. ## Footnote Use Case is a detailed description of how a system interacts with the end user or another system to achieve a specific goal.
43
What is the difference between Test Scenario vs Test Case?
Test Scenario created first from the Requirements. Then QA converts Test Scenarios into Test Cases. Test Scenario is about what we test and Test case is how to achieve that testing goal. Test Scenario is high level document (less detail) and Test Case is low level (detailed) document created by QA. ## Footnote Example: Test Scenario - User login functionality. Test Case - Verify user can log in with valid credentials.
44
What is Scrum?
It is daily stand up meeting where QA reports what they have done previous day and what they plan to do in the current day. ## Footnote No additional information.
45
What is STLC?
STLC stands for Software Testing Life Cycle. It is what QA does at work. ## Footnote Example sentence: QA follows STLC to ensure thorough testing of software.
46
What is Scope?
What is being tested by QA is called "IN Scope". What is not being tested by QA is "Not IN Scope". Scope simply means what we are working on. ## Footnote Additional information: Scope defines the boundaries of testing activities.
47
How do you do Requirements Analysis?
QA will read the requirements to identify any vague, incorrect, and contradictory statements. Is it Testable is the point of Req analysis. ## Footnote Example sentence: Requirements analysis is essential to ensure that testing can be effectively carried out.
48
What is the difference between USER Story vs Test Scenario?
User Story is a requirement created by BA. QA uses this User Story and creates usually multiple Test Scenario to test that 1 User Story ## Footnote Example: QA team creates Test Scenarios based on the User Story provided by the BA.
49
What is the difference between Use case vs Test Case?
Use case is a requirement created by BA. QA uses Use Case to create Test Scenarios and converts them into Test Cases. ## Footnote Additional information: Test Cases are derived from Test Scenarios, which are created based on the Use Case.
50
How do you create Test Case?
First QA gets the requirements from Business Analyst and analyze it for testability ## Footnote Example: QA receives the requirements document from the Business Analyst and reviews it to ensure it can be effectively tested.
51
What does QA do after analyzing requirements?
Then QA creates Test Scenario ## Footnote After analyzing the requirements, QA develops a Test Scenario based on the identified testable aspects.
52
What happens after creating Test Scenarios?
Afterwards QA converts Test Scenarios into Test Cases ## Footnote QA translates the Test Scenarios into detailed Test Cases that outline specific test steps and expected results.
53
What is Test Case ID?
Test Case ID - generated by the system (like ALM) ## Footnote This is a unique identifier assigned to each test case by the system, similar to ALM.
54
What is Test Description?
Test Description - this is exactly the same to Test Scenario; what you are trying to test ## Footnote Test Description is a brief explanation of what the test case is trying to achieve, similar to the Test Scenario.
55
What is Test Data?
Test Data - data that you will use for this testing ## Footnote Test Data refers to the specific data inputs that will be used during the testing process.
56
What are Test Steps?
Test Steps - actions you take ## Footnote Test Steps are the specific actions or procedures that need to be followed in order to execute the test case.
57
What is Expected Result?
Expected Result - intended outcome of your actions ## Footnote Expected Result is the anticipated outcome or behavior that should occur when the test case is executed successfully.
58
What is Actual Result?
Actual Result - result produced when you have taken the action described in Test Steps ## Footnote Actual Result is the outcome that is observed or recorded after performing the actions outlined in the Test Steps.
59
What is Status?
Status - Pass or Fail (actual result = expected result then Pass) ## Footnote Status indicates whether the test case passed or failed based on a comparison between the Actual Result and Expected Result.
60
What other information is included in a Test Case?
Notes, Author, Test Creation and Execution Date ## Footnote In addition to the main components of a test case, other information such as Notes, Author, and Test Creation and Execution Date may also be included for documentation and tracking purposes.
61
What is in Test Case
Test Case ID - generated by the system (like ALM) • Test Description - this is exactly the same to Test Scenario; what you are trying to test • Test Data - data that you will use for this testing Test Steps - actions you take • Expected Result - intended outcome of your actions • Actual Result - result produced when you have taken the action described in Test Steps • Status - Pass or Fail (actual result = expected result then Pass) • Notes • Author • Test Creation and Execution Date
62
What are the STLC Phases?
Requirements Analysis Test Planning Test Case Development Environment Setup Test Execution Test Closure (sign off)
63
What is Requirements Analysis?
requirement analysis is about reviewing project needs to see what should be tested and making sure those needs are clear and easy to test.
64
What is Test Planning?
Creating a strategy that outlines how, when, and what to test to ensure the software meets quality standards.
65
What is Test case Development?
creating step-by-step tests to check if the software works as expected.
66
TEST Execution/ Regression Cycle
**Test execution** is running tests to see if the software works properly. The **Regression cycle** is checking those tests again after any changes to ensure everything still works as it should.
67
What is Test Analysis
checking requirements to see what needs testing and outlining the scope to ensure quality.
68
What is Regression Testing?
Regression testing is the last testing you do before you sign off. It is one of the most important types of testing, in which you make sure everything still works. Dev can fix one function and break the other so you retest everything again to make sure the application still working. ## Footnote By: Hushnudbek Yulchiev
69
Who sets up Test Environment at work?
QA sets up Testing Environment ## Footnote Example sentence: QA team is responsible for setting up the Test Environment at work.
70
How do you know how to setup your Environment?
I get the Software/Hardware requirements from Developers on what are the Environment Requirements for this application. Then I simply set it up ## Footnote Example sentence: Understanding the requirements from Developers helps in setting up the Environment correctly.
71
How many Environments are there?
5 Environments - Development, QA, UAT, Production and DisasterRecovery Environments ## Footnote Example sentence: There are 5 different Environments in the software development lifecycle.
72
In which Env do you work?
QA tests in QA Env ## Footnote Example: Quality Assurance tests are conducted in the QA Environment.
73
Do you test in Production Env?
No at my previous companies QA doesn't have access to Production Env. ## Footnote Example: Quality Assurance team does not have access to the Production Environment in previous companies.
74
What testing is done by QA the first?
Smoke Testing is the first testing for QA when we, receive new build of the app within the Sprint. ## Footnote Example: Smoke Testing is the initial testing performed by Quality Assurance when a new build of the application is received during the Sprint.
75
If you found an extra functionality while testing what do you do?
I log a bug. Extra Functionality might bring unintended business or technical issues. ## Footnote Example sentence: If I found an extra functionality during testing, I would log a bug to address it.
76
What is the point of Requirment Analysis
Is it Testable, In order to find out if Requirment is Testable , Tester will read the Req to identify any vague, incorrect, contradictory statments
77
What is the point of Requirment Analysis
Is it Testable, In order to find out if Requirment is Testable , Tester will read the Req to identify any vague, incorrect, contradictory statments
78
Bug/Defect
Actual result doesn’t match with Expected result
79
What is Showstopper
It is a major issue that blocks software from working properly or being released, needing immediate fixing.
80
What is BUG Severity?
It is a technical side of the bug. QA assigns the severity of the bug. It is how much this bug is affecting the system. ## Footnote Example sentence: The QA team determined the BUG Severity of the issue to be critical.
81
What is Bug Priority?
Priority is business side - BA assigns the priority of the bug. What must be fixed now and what can be fixed later ## Footnote Example sentence: The BA identified the Bug Priority of the issue as high.
82
What is a Blocker?
Bug that doesn't let you to test further. QA is stuck, like application is crashing or QA can't login. ## Footnote Example sentence: The QA team encountered a Blocker bug that prevented further testing.
83
What is Bug Life Cycle
New, Open, Fixed, Closed
84
What do you do when you find a defect?
Reproduce it at least twice. Look for any duplicates in the system. Then log the bug and assign it to Developer ## Footnote Example: If I find a defect in the login screen, I will try to reproduce it by entering different combinations of incorrect credentials.
85
What bugs must be fixed within the same Sprint?
High Priority bugs ## Footnote It is crucial to prioritize high priority bugs to ensure the sprint goals are met on time.
86
What do you do if the bug is not fixed when you retest?
I assign it back to the Developer. Simply reopen ## Footnote Reopening a bug that was not fixed ensures that it gets the necessary attention for resolution.
87
What is BUG ID?
generated by the system you are using; for ex: JIRA ## Footnote Unique identifier for the bug ticket
88
What is Product?
which application is affected ## Footnote Application impacted by the bug
89
What is Component?
what part of the application is affected ## Footnote Specific area of the application impacted by the bug
90
What is Bug Title?
Summary that explains easily what was observed ## Footnote Brief description of the bug
91
What is BUG Description?
actual result observed and what was expected ## Footnote Detailed explanation of the bug
92
What are Steps to Reproduce?
steps to follow to get to the bug ## Footnote Sequence of actions to recreate the bug
93
What are Attachments?
any screenshots or log files ## Footnote Additional files that provide more context for the bug
94
What is Environment?
in which environment the bug was found ## Footnote System configuration where the bug occurred
95
What is Version?
build number of the app you found the bug in ## Footnote Software version where the bug was discovered
96
What is Priority?
how important this bug is for the business ## Footnote Level of urgency assigned to the bug
97
What is Severity?
how this bug is affecting the system/technical ## Footnote Impact of the bug on the system or functionality
98
What is Status?
whether the bug still open or fixed or verified ## Footnote Current state of the bug resolution process
99
What is Author & Date?
Information about who reported the bug and when ## Footnote Person who identified the bug and the date it was reported
100
What goes into the Bug Ticket
Bug ID Bug Title Product Component Bug Description Steps to Reproduce Attachments Environment Version Priority Severity Status Author Dates
101
Automation QA vs Manual QA
Automation QA -who writes scripts that will run in an application that will test the other software Manuel QA - who does exact same thing as above but manually
102
Ad Hoc testing
it means testing without any requirements exp: Sometimes BA gets sick or leaves but the job continues
103
Exploratory Testing
Testing in order to learn the application exp: When you dont have any requirements and dont know the application, so you just click around and learn it
104
Alpha Testing
all QA testing is called Alpha Testing (Black Box Alpha testing)
105
Boundry Testing
You test the boundaries
106
Integration Testing
testing functionalities working well together exp: Press gass pedal and car goes faster
107
Accessability Testing
It is testing that an application can be used by Dead or Blind people
108
Risk based testing
It is prioritizing most users used functionalities complex areas, high business priority functions
109
Code Drop
It is simply installing the application into QA environment so that you can test. Who instals it? Usulay Devolopers , QA simply writes email to have the certain version of the QA env and Developer will install it.
110
Bug vs Enhancement
Bug is actual result doesnt match the expected result, -When functionality doesnt behave as per the requirements. Enhancement is on the other hand is a suggestion for improvement.
111
Target vs Full Regression testing
Full Regression Testing involves testing all the functionalities of the application Targeted regression testing is testing only affected areas if only specific areas of the application is effected by code.
112
Sanity Testing
Before retesting of fixed bugs, Retest is simply verifying that bug are indeed fixed. Testing withing the sane release whatever you recieve a new version of the app
113
Whats the difference between Black box vs White box
Black box tester- doesn’t know anything about coding. Almost everyone are black box testers White/ Glass box tester tests the code directly. There are very few white box testers.
114
Whats the difference between Black box vs White box
Black box tester- doesn’t know anything about coding. Almost everyone are black box testers White/ Glass box tester tests the code directly. There are very few white box testers.
115
What is RTM
Requirement Traceability Matrix. It is simply mapping of Test Cases to the requirements

QA Methodology (3 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2025 Bold Learning Solutions. Terms and Conditions