Testing Flashcards
1
Q
Which test management tools did you use before? Do you like it? And why?
A
In my current project we are using Zephyr. Zephyr uses structured and freeform test execution cycles, and is easy to use.
2
Q
What is a test cycle?
A
A test cycle is a container for tests and test suites that spans multiple users and projects.
3
Q
How to create test cycle in Zephyr?
A
Click on Plan Test Cycle, add and execute tests as part of those cycles.
4
Q
What is a Smoke Test Suite?
A
A smoke test suite combines a number of smoke tests into a small suite of tests so that when the application is ready to deliver to staging or pre-production, developers will know in a matter of minutes whether the latest version of their application is ready for further QA and review.
Smoke tests are also used at times in emergencies or when teams want to release a hot patch for their production applications.
5
Q
What is Testing
A
The process of verifying and validating that a software is bug free, meets all requirements with handling all the exceptional and boundary cases
6
Q
What is the software development life cycle?
A
Conceptual model used in project management that describes the stages involved in an information system development project, from an initial feasibility study through maintenance of the completed application.
7
Q
What is SDLC
A
Software development life cycle
8
Q
Why is an understanding of SDLC is important to Software QA Engineers?
A
SDLC includes Requirement phase, Design phase, Coding (programming), Testing, Release (Production), Maintenance (Support).
Testing is one of the most important components of the software development lifecycle Quality assurance is the planned and systematic set of activities that ensures that software processes and products conform to requirements, standards, and procedures.
9
Q
What is Agile Software Development Model
A
Agile software development is a set of principles for software development in which requirements and solutions evolve through collaboration between self-organizing, cross-functional teams
The Agile movement seeks alternatives to traditional project management. Agile approaches help teams respond to unpredictability through incremental, iterative work cadences, known as sprints. Agile methodologies are an alternative to waterfall or traditional sequential development.
10
Q
When to use Agile model:
A
- When new changes are needed to be implemented. The freedom agile gives to change is very important. New changes can be implemented at very little cost because of the frequency of new increments that are produced.
- To implement a new feature the developers need to lose only the work of a few days, or even only hours, to roll back and implement it.
- Unlike the waterfall model in agile model very limited planning is required to get started with the project. Agile assumes that the end users’ needs are ever changing in a dynamic business and IT world. Changes can be discussed and features can be newly effected or removed based on feedback. This effectively gives the customer the finished system they want or need.
- Both system developers and stakeholders alike find they also get more freedom of time and options than if the software was developed in a more rigid sequential way. Having options gives them the ability to leave important decisions until more or better data or even entire hosting programs are available; meaning the project can continue to move forward without fear of reaching a sudden standstill.
11
Q
Main differences between Waterfall and Agile
A
Agile
- things are done in parallel
- new features come every week and there is not enough time and resources to do things stage by stage
- provides flexibility, which makes it more bug free and more inclined towards better client satisfaction.
Waterfall model
- has no flexibility
- does not allow any modifications once the module is completed
- in case of changes we’d have to build the entire project from scratch
- testing can be done only at the end of development module.
12
Q
What does ‘Sprint’ in Agile development mean?
A
In product development, a sprint is a set period of time during which specific work has to be completed and made ready for review.
13
Q
What is the typical ‘Sprint’ duration?
A
Some people would say that the two weeks sprint has become the industry standard, but in the reality, sprint duration could be completely different. It could vary from 1 to 4 weeks and highly depends on the company, team and the project and what will work best for them.
14
Q
Scrum Master responsibilities
A
- Facilitating (not participating in) the daily standup.
- Helping the team maintain their burndown chart.
- Setting up retrospectives, sprint reviews or sprint planning sessions.
- Shielding the team from interruptions during the sprint. -Removing obstacles that affect the team.
- Walking the product owner through more technical user stories.
- Encouraging collaboration between the Scrum team and product owner.
15
Q
Product Owner responsibilities
A
- Responsible for collecting all the information from the stakeholders and presents it in one prioritize list for the team.
- PO is the one who can accept or reject the work.
- Responsible for maximizing the value of the product and work of the development team.
- Sole person responsible for managing product backlog.
16
Q
QA tester responsibilities
A
- attend sprint-planning session. This ensures QA is in sync with development team from the start and allows QA to identify possible problem areas and risks early on.
- attend daily stands up. This promotes a collaborative team environment, making QA feel involved and part of the team.
- do testing throughout the entire duration of the sprint, the workload for QA should be spread out and this allows for issues to be found earlier instead of only at the end.
- schedule a quick face to face handoff demonstration for each feature with the developer. This allows QA to see exactly how to the new feature works and is a good time for them ask the developer any questions.
- attend sprint retrospectives. Sprint retrospectives are the opportunity to define weakness and determine solutions for them.
17
Q
Typical Agile team consists of:
A
- 1 product owner
- 1 scrum master (project manager)
- 5 developers
- 2 QA
18
Q
What is Software Quality Assurance?
A
Software quality is a perceptual and conditional thing.
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 the gathering of requirements, design, and reviews to coding, testing, and implementation.
19
Q
What is software testing?
A
Software testing is a process of executing a program or application with the intent of finding software bugs.
It can also be 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 and can be implemented with the same characteristic
20
Q
What is the difference between Software Testing and Software QA?
A
Testing is mainly an ‘error detection’ process focusing on improving the source code.
Software QA is ‘preventative’ aiming 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).
21
Q
Why is software quality not perfect?
A
You can’t find all bugs in software,
Not all bugs which are found will be fixed.
To make perfect software takes a long time but, in reality, we do have not enough time to fix all the bugs.
22
Q
What is adhoc testing?
A
AD HOC TESTING is a method of software testing without any planning and documentation.
The tests are conducted informally and randomly without any formal procedure or expected results.
“Monkey testing”
23
Q
What is a Bug?
A
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.
24
Q
Bug report components are?
A
- Short summary (Bug Title)
- Environment
- Steps to reproduce
- Expected and actual results
- Attachments if applicable
25
What t is JQL?
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.
26
How you can search in Jira?
Using basic and advanced search.
27
What is Confluence?
What kind of data you can find in Confluence?
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
28
What is a test case?
A set of test inputs, execution conditions, and expected results developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement.
29
What are the most important components of test cases?
• 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
30
What is a Check List?
A checklist is a catalog of items/tasks that are recorded for tracking. This list could either be ordered in a sequence or 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.
31
What is Test Suite?
- a collection of test cases that are intended to be used to test a software program to show that it has a specified set of behaviors.
- 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.
32
How many test cases can you create if you don't have requirements?
Begin with testing it based on common sense.
When 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 collected, create a test plan and try to get a second opinion on it, probably by sending my doc to PM and QA manager.
33
How do you write test cases?
1. Freestyle
| 2. Gherkin style.
34
What is Smoke test (also confidence testing, sanity testing)
-superficial build acceptance.
- refers to the first test made after assembly or repairs to the system, to provide some assurance that the system under test will not catastrophically fail.
--is light type testing, objective is figure out, to verify that all build works, is a alive.
When the application is released in testing environment the QA team started smoke test.
35
What is Sanity Testing?
- smoke test is a quick test to see that after a build the application is good enough for testing
- sanity test tells you if a particular functional area is good enough that it actually makes sense to proceed with tests on this area
36
What is Bug triage
- to evaluate, prioritize and assign the resolution of defects.
- The team needs to validate the severity of the defect, make changes as per need, finalize resolution of the defects, and assign resources.
--Mainly used in agile project management.
37
What is bug Severity and Priority?
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.
38
How is mobile testing and mobile app testing different?
Mobile testing means checking the functionalities of a mobile device while mobile app testing means testing applications running over mobile devices.
39
What are the four types of common bugs?
critical, block, minor, and major.
40
Give an example of common mobile bugs and how you prioritize them
testers work to find four types of common bugs; critical, block, minor, and major
- a phone system crash when testing a particular feature of the device will be classified as a critical bug.
T-the GUI bugs will be categorized as minor bugs
- functional disability of a particular feature will be submitted to a major bug list
- Certain performance unavailability through the device is ON will fall into the block bug list
41
What are the types of mobile applications?
* Native apps are created for one specific platform or operating system.
* Web apps are responsive versions of websites that can work on any mobile device or OS because they’re delivered using a mobile browser.
* Hybrid apps are combinations of both native and web apps, but wrapped within a native app, giving it the ability to have its own icon or be downloaded from an app store.
42
What according to you is the importance of Usability testing?
Usability testing is used to check if the app is user-friendly.
It involves analyzing customer’s behavior and experience on the application to identify bugs and discrepancies.
The metrics considered for usability testing are the design of the app, response time and how intuitive it is.
43
What is the latest version of iOS?
IOS 15
44
What is the latest version of Android?
Android 12
45
What is the extension of Android files?
.apk (Android application package)
46
How would you define AVD?
AVD stands for Android Virtual Device.
It is an Android emulator to test applications on PCs.
47
What is the extension of iOS files?
.ipa (iOS App Store Package)
48
What are all major networks to be considered while performing application testing?
You should test the application on 4G, 3G, 2G, and WIFI.
2G is a slower network, it’s good if you verify your application on a slower network also to track your application performance.
49
What are the tools based on cloud-based mobile testing?
Perfecto Mobile, AWS Device Farm, BrowserStack, SauceLabs.
50
What is the most common problem with the emulators according to you?
They often fail to capture the important attributes of a device.
They have a lot of compatibility issues if no open source technology is considered.
51
How would you define a good test case?
Good test case: Here is an example of a good test case: install and launch the application. Try to login with user info@interview.com with password “abcd”, wait 5 seconds for the app to respond and shows you the app interface after the login.
52
How would you define a bad test case?
There can be two main bad test case scenarios.
The first one would be very undescriptive, e.g. install, launch and login. In this case you don’t really know what to expect exactly from the test.
The other bad test case would be a test case that tries to test many different functionalities at the same time. The result would be that you don’t concentrate on just one aspect of the app at a time and you might be missing other important functionality.
53
What metrics are considered when sanity test is performed on mobile apps?
The sanity test on apps can be performed based on 5 metrics:
1. Performance on different devices.
2. Performance in various network environments.
3. Installation and update of apps.
4. If the app allows calls when running in the background.
5. Media compatibility.
54
What is WAP?
WAP stands for Wireless Application Protocol. Used in network apps, this communication protocol enables data access through wireless networks.
It facilitates easy connectivity between mobiles and the internet and enhances wireless interoperability.
55
How do you communicate app crashes to the developer?
Identify the scenario in which the app crashes.
Use a defect tracking tool to report app crashing
Steps to reproduce to bring app crashes in control.
Attach screenshots with the error message.
56
What would you do if your app works well on some devices and crashes on others?
Conduct compatibility tests to analyze the application’s performance on multiple devices with different network environments.
This will help in the identification of the devices on which the app crashes.
Try uninstalling and installing the app and if it still does not function properly, I would highlight the issue to the developer and suggest fixes.
57
Can you name 2 apps for Android and iOS each to record crash logs?
To record crash logs, you can use
- Android Studio and Eclipse for Android devices
- iOS LogInfo and Xcode iOS devices.
58
What are the most important mobile application test cases ?
```
In my opinion, the most important mobile app test cases are:
• Usability test case.
• Battery usage test case.
• app functioning test case.
• Touchscreen test case.
• Security test case.
```
59
Difference between sanity and smoke testing
Sanity testing is a quick check of a bug fix or something specific in a new build. Shouldn't take longer than a minute or so.
Whereas, a smoke test is a quick test of the major functionality of an application.
60
Bug
An error, flaw or fault in a computer program that causes it to produce an incorrect or unexpected result, to behave in unintended ways
61
Defect
An imperfection or deficiency in a work product where it does not meet its requirement or spec
62
Error
a human action that produces an incorrect results
63
Test case
A set of preconditions, inputs, actions, expected results , post conditions, developed based on test conditions
64
Ad Hoc Testing
Random testing or monkey testing
| method of software testing without any planning and documentation
65
Functional testing
system is tested against the functional requirements/specs
| System is functioning as it should
66
Black box testing
you don't know and don't care how it works under the hood--no use of programming
67
Verification
confirmation by exam that specified requirements have been fulfilled--are you building the right product
68
Functional testing
system is tested against the functional requirements/specs
69
Compatibility testing
testing to check whether your software is capable of running on different hardware, operating systems, applications, network environments or mobile devices
70
Localization testing
product is checked to assure that it behaves according to the local culture or settings (language, currency, date and time format)
71
performance testing
determining the speed, responsiveness and stability of a software program or device under a workload.
Automated testing
72
Compatibility testing
to check whether your software is capable of running on different hardware, operating systems, applications, network environments or mobile devices
73
security testing
determines if an information system protects data and maintains functionality as intended
74
grooming
an open discussion between the product owner and the development team
75
scrum
framework for project management that emphasizes teamwork, accountability and iterative progress toward a well defined goal
76
JIRA
tool for bug/issue tracking and project management
77
software bug
error or flaw in a computer program that causes it to produce an incorrect or unexpected result or to behave in unintended ways
78
Bug triage
process where each bug is prioritized based on it severity, frequency, risk, etc by PO,BA, QA
79
Bug report must have:
```
Browser using
Operating system use
Error messages if any
Steps taken to reproduce
Screen shot with arrows/etc on it
```
80
Severity
the degree of impact on the development or application
| Priority is the order in which a defect should be fixed
81
Test case
a set of actions executed to verify a particular feature or functionality of the software and clarifies what you are doing to test the system
82
Test case
measures the quality of the application
83
Difference between a test case and a defect:
A defect/bug is written when something fails A, B and C didn’t happen and you went to F
A Test case is written to pass or work in a valid manner (negative or positive) verify that A, B and C happen
84
Bugs are
failed test cases
85
Write a Test case
Go into Jira
Hit Create button
Select issue type to be “test”
Scroll down to Zeyphyr test step section (if you don’t see it go into “Configure fields” and select all)
86
Test cases should
= 3-5 steps
87
Smoke testing
builds verification of software by ensuring important functions work and the build is stable
small set of test cases to ensure that most of the important functions work/shows if a build is stable enough to proceed with further testing/Bugs are usually P1 critical priority
88
Test plan
the blueprints for testing and making sure you are testing what you should be testing
89
Sanity Testing
testing performed after the software build to ascertain if bugs have been fixed and no further issues have been introduced due to changes
90
Smoke VS Sanity
Smoke is a quick test of major functionality while sanity is a quick test of particular functionalities /features /fixed bugs
91
Mind Mapping
a graphical representation of ideas and concepts using creative /logical way of advanced note-taking using symbols, colors, minds shapes, words, lines and images. (Coggle)
92
Regression testing
- all integration test cases
- all complex test cases
- boundary value test cases
- sample of successful test cases
- same of failure test cases
93
Regression test selection
- Don't re-execute the entire test suite--select parts of the test suite to be run
- Reusable test cases
- obsolete test cases
- reusable test cases can be used in succeeding regression cycles
- obsolete test cases can't be used in succeeding cycles
94
Gerkin
-used to write test cases for regression testing using advanced style
95
How to write Gherkin style test cases
capitalized when inputting into Jira for GIVEN, WHEN,THEN, and AND.
96
To work with the DOM or CSS
- right-click an element on the page and select Inspect to jump into the Elements panel
- Or press Command+Option+C (Mac) or Control+Shift+C (Windows, Linux, Chrome OS)
97
to see logged messages or run JavaScript
press Command+Option+J (Mac) or Control+Shift+J (Windows, Linux, Chrome OS) to jump straight into the Console panel.
98
to save console log
* Right click inside the Console tab
| * Click save as
99
In general, use the Network panel when you need to make sure that resources are being downloaded or uploaded as expected. The most common use cases for the Network panel are:
Making sure that resources are actually being uploaded or downloaded at all.
Inspecting the properties of an individual resource, such as its HTTP headers, content, size, and so on.
Time. How long the request took.
100
Accessibility audit
| To audit a page:
Go to the URL that you want to audit.
In DevTools, click the Lighthouse tab. DevTools shows you various configuration options.
Using the current tool you can check if your website is considered accessible if it can be perceived, understood, navigated and interacted with by everyone, whether or not they happen to have disabilities.
Web accessibility means that websites, tools, and technologies are designed and developed so that people with disabilities can use them
101
End-to-end testing
used to test whether the flow of an application is behaving as expected right from start to finish. The purpose of performing end-to-end testing is to identify system dependencies and to ensure that the data integrity is maintained between various system components and systems.
102
Key Steps in Setting up End-to-End Tests:
• Review the requirements you’ll be using end-to-end testing to validate.
• Set up the test environments and outline the
hardware/software requirements.
• Define all the processes of your systems and their integrated subsystems.
• Describe the roles and responsibilities for each system
• Outline the testing methodologies you plan to use and any testing standards (i.e., language, tools).
• Create the requirements for tracking and designing your test cases.
• List the input and output data for each system.
103
What is SQL?
- Structured Query Language
| - a database computer language, designed to retrieve and manage data, create and modify DB schema, etc.
104
What is a Database?
Systematically organized or structured repository of indexed information that allows easy retrieval, updating, analysis, and output of data.
105
What is a Query?
your request to the database to retrieve information.
106
What is the DBMS?
- Database Management System
| - software that controls the organization, storage, retrieval, security and integrity of data in a database.
107
What is a Primary Key?
- a unique identifier of every record in the database table
- a column in a database where each row has a unique value.
- Each table has only one primary key
- No NULL values are allowed.
- in a list of American citizens, the column with social security numbers (SSN) would be a Primary Key
108
Unique Key
- a column or group of columns that together hold unique values.
- A table can have more than one unique key.
- in a list of American citizens, the first and last name columns combined with phone number would be a Unique Key.
109
What is a SQL Join
an instruction to combine data from two sets of data
110
SQL Join Example
- find all orders placed by a particular customer.
| - do this by joining the customers and orders tables together using the relationship established by the customer_id key.
111
Inner Join
-return rows when there is at least one match of rows between the tables.
112
Inner Join
return rows when there is at least one match of rows between the tables.
113
Right Join
return rows that are common between the tables and all rows of the right-hand side table. Simply, it returns all the rows from the right-hand side table even though there are no matches in the left-hand side table.
114
Left Join
return rows that are common between the tables and all rows of the left-hand side table. Simply, it returns all the rows from the left-hand side table even though there are no matches in the right-hand side table.
115
Full Join
return rows when there are matching rows in any one of the tables. This means that it returns all the rows from the left-hand side table and all the rows from the right-hand side table.
116
What are Tables and Fields?
A Table is a set of data that is organized in a model with Columns and Rows.
Columns can be categorized as vertical, and Rows are horizontal.
A Table has a specified number of Columns called
Fields but can have any number of Rows that are called a record.
117
What is a Stored Procedure?
a function that consists of many SQL statements to access the database system.
118
What is the DELETE Command
A DELETE command is used to remove rows from the table, and a WHERE clause can be used for a conditional set of parameters.
Commit and Rollback can be performed after a delete statement.
119
What is the TRUNCATE Command
The TRUNCATE command removes all rows from a table, but the table structure and its columns, constraints, indexes, and so on remain.
120
What is a Constraint?
- can be used to specify the limit on the data type of table.
- A constraint can be specified while creating or altering the table statement.
```
Sample of constraints are:
NOT NULL
CHECK
DEFAULT
UNIQUE
PRIMARY KEY
FOREIGN KEY
```
121
What is CLAUSE?
A SQL clause is defined to limit the result set by providing the condition to the query.
122
What is API
Application Programming Interface
- acts as an intermediary layer that processes the data transfer between systems
- Using FB to send an IM
123
What are the 2 types of API?
1- SOAP-simple object access protocol-defines standards like security and how to send messages
2-REST-representational state transfer-defines a set of functions for sending requests and receiving responses (HTTP protocol methods)
124
What is REST?
- acronym -Representational State Transfer
| - first presented by Roy Fielding in 2000 in his famous dissertation.
125
6 architectural constraints of REST are?
1. Client-Server – By separating the user interface concerns from the data storage concerns, we improve the portability of the user interface across multiple platforms and improve scalability by simplifying the server components.
2. Stateless – Each request from the client to server must contain all of the information necessary to understand the request, and cannot take advantage of any stored context on the server. Session state is therefore kept entirely on the client.
3. Cacheable – Cache constraints require that the data within a response to a request be implicitly or explicitly labeled as cacheable or non-cacheable. If a response is cacheable, then a client cache is given the right to reuse that response data for later, equivalent requests.
4. Uniform Interface – By applying the software engineering principle of generality to the component interface, the overall system architecture is simplified and the visibility of interactions is improved. In order to obtain a uniform interface, multiple architectural constraints are needed to guide the behavior of components. REST is defined by four interface constraints: identification of resources, manipulation of resources through representations, self-descriptive messages, and hypermedia as the engine of the application.
5. Layered System – The layered system style allows an architecture to be composed of hierarchical layers by constraining component behavior such that each component cannot “see” beyond the immediate layer with which they are interacting.
6. Code on Demand (optional) – REST allows client functionality to be extended by downloading and executing code in the form of applets or scripts. This simplifies clients by reducing the number of features required to be pre-implemented.
126
What is API Testing ?
--a software testing type that validates the Application Programming Interface (API).
-- purpose of API Testing is to check the functionality, reliability, performance, and security of the programming interfaces
--you use software to send calls to the API, get output, and note down the system's response.
127
REST uses a specific HTTP methods
| What are the most common HTTP methods:?
A GET request fetches a record from a database
A POST request adds a new record to a database
A PUT request replaces a record with a new one
A PATCH request replaces part of a record with new information
A DELETE request removes a record from a database
128
What is Postman?
Postman is an excellent choice to test API's for those who do not want to deal with coding in an integrated development environment, using the same programming language as a developer would use.
129
What is Soap UI?
With SoapUI, users can get the full source document and embed their preferred set of features, in addition to those listed below:
Create a test quickly and easily using drag-and-drop and point-and-click techniques
Powerful data-driven testing: Loaded from files, databases and Excel, so they can simulate user and API interactions.
Create complex scripts and support asynchronous testing
130
What is Jmeter?
JMeter (a open source software) is widely used for functional testing of APIs
Supports playback of test results
Automatically handles CSV files
Can be used for both static and dynamic resource performance testing
131
What is ApiGee?
Apigee is a cross-cloud API testing tool
Allows you to develop, monitor, deploy and scale APIs
Identifies problems by tracking API traffic, error rates and response times
Designed specifically for digital business and data-intensive tasks on mobile API platforms and applications that manage it
132
What is Assertible?
Assertible is an API testing tool that focuses on process automation and reliability.
Provides automated API testing at every stage of the software integration and delivery process
Provides support for ongoing API tests after application deployment
Supports authentication of HTTP responses with out-of-the-box error-free confirmation statements
133
What is Katalon Studio?
Katalon Studio supports SOAP and RESTful requests with different types of commands (GET, POST, PUT, DELETE).
Support for a combination test between UI and API verifications
Support for testing both SOAP and RESTful requests
Can be used in both automated and exploratory testing
134
Why Use Postman?
- over 4 million users
1. Accessibility - To use Postman, you just need to log into your account making it easy to access files anytime, anywhere as long as a Postman application is installed on the computer.
2. Use of Collections - Postman lets users create collections for their API calls. Each collection can create subfolders and multiple requests. This helps in organizing your test suites.
3. Collaboration - Collections and environments can be imported or exported making it easy to share files. A direct link can also be used to share collections.
4. Creating Environments - Having multiple environments aids in having less repetition of tests as one can use the same collection but for a different environment. This is where parameterization will take place, as we will discuss in further lessons.
5. Creation of Tests - Test checkpoints, such as verifying for successful HTTP response status, can be added to each API call to help ensure test coverage.
6. Automation Testing - Through the use of the Collection Runner or Newman, tests can be run in multiple iterations saving time for repetitive tests.
7. Debugging - Postman console helps to check what data has been retrieved making it easy to debug tests.
8. Continuous Integration - With its ability to support continuous integration, development practices are maintained.
135
What is an API?
- API is an acronym for Application Programming Interface.
- An API is a set of routines, protocols, and tools for building Software Applications.
- APIs specify how one software program should interact with another software program.
136
What is API Testing?
- a type of software testing that involves testing APIs directly and also as part of integration testing, to check whether the API meets expectations in terms of functionality, reliability, performance and security of an application.
- main focus will be on the business logic layer of the software architecture.
- can be performed on any software system which contains multiple APIs.
137
What is Rest API?
--stands for Representational State Transfer.
--a set of functions helping developers in performing requests and receiving responses
- Interaction are made through the HTTP Protocol in REST API.
138
What are the common tests that are performed on APIs?
1. Verify whether the return value is based on the input condition. The response of the APIs should be verified based on the request.
2. Verify whether the system is authenticating the outcome when the API is updating any data structure.
3. Verify whether the API triggers some other event or request another API.
4. Verify the behavior of the API when there is no return value.
139
What exactly needs to be verified in API Testing?
with API Testing, we send a request to the API with the known data and we analyse the response.
1. Data accuracy;
2. HTTP status codes;
3. Response time;
4. Error codes in case API returns any errors;
5. Authorization checks;
6. Non-functional testing such as performance testing and security testing.
140
Name some tools used for API Testing
Postman, Katalon
141
Some of the more popular API examples are:
* Google Maps API
* YouTube
* Twitter
* Amazon Advertising API
142
Name some of the most commonly used HTTP methods
GET: It enables you to retrieve data from a server
POST: It enables you to add data to an existing file or resource in a server
PUT: It lets you replace an existing file or resource in a server
DELETE: It lets you delete data from a server
PATCH: It is used to apply partial modifications to a resource
143
What is the API test environment?
--a complex method where the configuration of the server and database is done as per the requirements of the software application.
--Graphical User Interface (GUI) is not available in this form of testing.
--After installation, the API is verified for its proper functioning.
--In this process, the initial environment that invokes API is being set up with a defined set of parameters so that test results can be examined.
144
What is an API collection?
--a grouping of requests.
145
What is the Environment in Postman?
--a set of key-value pairs.
--An environment helps us to differentiate between the requests.
