Learn API Testing
Norms, Practices, and Guidelines for Building Effective Test Automation
(Sprache: Englisch)
Explore software web application architecture, API testing, coding practices, and the standards for better API test automation development and management. This book focuses on aspiring software testing engineers currently working in API testing, and those...
Voraussichtlich lieferbar in 3 Tag(en)
versandkostenfrei
Buch (Kartoniert)
60.49 €
- Lastschrift, Kreditkarte, Paypal, Rechnung
- Kostenlose Rücksendung
- Ratenzahlung möglich
Produktdetails
Produktinformationen zu „Learn API Testing “
Klappentext zu „Learn API Testing “
Explore software web application architecture, API testing, coding practices, and the standards for better API test automation development and management. This book focuses on aspiring software testing engineers currently working in API testing, and those starting their journey in the field of software testing. You'll begin with an introduction to API testing and software web applications involving APIs. The book then moves on to the authentication standards used in the software industry, and the tools, the frameworks, and the libraries used in API testing. As the book progresses, you'll learn about the test pyramid, how to test an API, what makes a good test script, and various coding guidelines. Finally, you get to write your own API test script.
Learn API Testing is your pathway to understanding a typical software web application, its requests and responses, and the properties of a good test script.
What You'll learn
- Examine practices, standards, and guidelines for effective test automation
- Work with different tools like RestAssured, Curl, and Postman
- Understand API testing paradigm (internal/external APIs, CDCT)
- Review a case study on the industrial software API testing process
- Organize a test framework
Who This Book Is For
API testing aspirants, developers/architects, project managers, and non-technical team members who may want to understand how APIs are being tested.
Inhaltsverzeichnis zu „Learn API Testing “
Chapter 1: Introduction to API TestingChapter Goal: Help the reader identify the purpose of the book, target audience and skills set required to perform API Testing
No of pages -
Sub -Topics
1. What is API Testing
2. Why We Need API Testing
3. Types of API Testing
4. AdvantagesChapter 2: Software Application
Chapter Goal: Gain knowledge about software web application standards which involves APIs
No of pages: -
Sub - Topics
1. REST Client/Server Architecture
2. Monolithic Vs. Microservices based web application
3. HTTP(s)
4. Header(s)
5. Request / Response
6. Response CodesChapter 3: Authentication
Chapter Goal: Standard authentication used in industry
No of pages : -
Sub - Topics:
1. Basic Authentication
2. Session Based Authentication
3. Token / JWT Based Authentication
4. OAuth2 Based AuthenticationChapter 4: Tools
Chapter Goal: Understanding of Tools used for doing API Testing
No of pages: -
Sub - Topics:
1. Postman2. CURL
3. RestAssured
4. TestNG
5. Log4j
6. Java - Spring BootChapter 5: Test Pyramid
Chapter Goal: Testing types and hierarchy of each type
No of pages: -
Sub - Topics:
... mehr
1. Black Box Testing
2. Grey Box Testing
3. Unit Testing
4. Components of Test PyramidChapter 6: Testing The API
· Chapter Goal: API Testing Paradigm (Internal/External APIs., CDCT)
No of pages: -
Sub - Topics:
1. Manual Test Script/ Workflows/ Use Cases
2. What to Test
a. Schema
b. Data
c. Data Type
3. Coverage Good / Bad
4. Headers Testing
a. Request Header
i. Correct Header
ii. Missing Header
iii. Incorrect Header
iv. Unsupported Type
b. Response Header
i. Supported Type
ii. Header Response
iii. Response Codes
5. Request Body
a. Format Unsupported
b. Special Characters
c. Too long String
d. Invalid value
e. Wrong data type
f. Empty data/object
g. Required fields
h. Null
i. Redundant fields
j. DELETE already deleted entity
k. Use PUT in place of POST etc.
6. Response Body
a. Actual Data vs. Expected Data
b. Limit
7. Internal vs. External APIs8. CDCT - Consumer Driver Contract Testing
9. Risk
a. Importance of Negative TestingChapter 7: A Good Test Script
Chapter Goal: Properties of a Good test script
No of pages: -
Sub - Topics:
1. Components of a Good Test Script
2. Example
Chapter 8: Coding Guidelines
Chapter Goal: Using standard coding guidelines for better test management and review.
No of pages: -
Sub - Topics:
1. Google Best Practices
2. Test Naming Conventions
3. Method Naming Convention
4. OthersChapter 9: Organize Test Framework
Chapter Goal: Organize a test framework in a way that is usable across any team / project
No of pages: -
Sub - Topics:
1. Maven Project
2. Dependencies3. Spring Boot
4. Properties File/Environment Based
5. End Points
6. Authentication
7. Request
8. Response
9. Test Data
a. JSON
b. File
c. HashMapd. TestNG data provider
10. LoggingChapter 10: First Test
Chapter Goal: Write first test to get a feel of API testing
No of pages: -
Sub - Topics:
1. Developing First Test
2. Executing First Test
3. Check Results
4. Check Logging
Chapter 11: API Documentation
Chapter Goal: API documentation is a mandatory requirement for writing API tests, swagger is the tool that is being used, we will see how to read the swagger API documentation for better understanding on the End Points.
No of pages: -
Sub - Topics:
1. Swagger
2. Why We Need API Documentation
3. Understanding the API Documentation
Chapter 12: Case Study - Shopping Cart APIs
Chapter Goal: A Sample application is used to demonstrate the industrial way of doing API testing, this is an equivalent to a workshop on doing API testing.No of pages: -
Sub - Topics:
1. Setting Up Application
2. Goal Setting
3. Test Environment (Docker Container)
4. Test Data Preparation
5. Agile Testing
6. Shopping Cart API End Points
7. Understanding Business Requirements
8. Manual Tests Scripts
9. Implementing Test Framework
10. Writing Test
11. Test Suite12. Execution
13. Results
14. Utilities
1. Black Box Testing
2. Grey Box Testing
3. Unit Testing
4. Components of Test PyramidChapter 6: Testing The API
· Chapter Goal: API Testing Paradigm (Internal/External APIs., CDCT)
No of pages: -
Sub - Topics:
1. Manual Test Script/ Workflows/ Use Cases
2. What to Test
a. Schema
b. Data
c. Data Type
3. Coverage Good / Bad
4. Headers Testing
a. Request Header
i. Correct Header
ii. Missing Header
iii. Incorrect Header
iv. Unsupported Type
b. Response Header
i. Supported Type
ii. Header Response
iii. Response Codes
5. Request Body
a. Format Unsupported
b. Special Characters
c. Too long String
d. Invalid value
e. Wrong data type
f. Empty data/object
g. Required fields
h. Null
i. Redundant fields
j. DELETE already deleted entity
k. Use PUT in place of POST etc.
6. Response Body
a. Actual Data vs. Expected Data
b. Limit
7. Internal vs. External APIs8. CDCT - Consumer Driver Contract Testing
9. Risk
a. Importance of Negative TestingChapter 7: A Good Test Script
Chapter Goal: Properties of a Good test script
No of pages: -
Sub - Topics:
1. Components of a Good Test Script
2. Example
Chapter 8: Coding Guidelines
Chapter Goal: Using standard coding guidelines for better test management and review.
No of pages: -
Sub - Topics:
1. Google Best Practices
2. Test Naming Conventions
3. Method Naming Convention
4. OthersChapter 9: Organize Test Framework
Chapter Goal: Organize a test framework in a way that is usable across any team / project
No of pages: -
Sub - Topics:
1. Maven Project
2. Dependencies3. Spring Boot
4. Properties File/Environment Based
5. End Points
6. Authentication
7. Request
8. Response
9. Test Data
a. JSON
b. File
c. HashMapd. TestNG data provider
10. LoggingChapter 10: First Test
Chapter Goal: Write first test to get a feel of API testing
No of pages: -
Sub - Topics:
1. Developing First Test
2. Executing First Test
3. Check Results
4. Check Logging
Chapter 11: API Documentation
Chapter Goal: API documentation is a mandatory requirement for writing API tests, swagger is the tool that is being used, we will see how to read the swagger API documentation for better understanding on the End Points.
No of pages: -
Sub - Topics:
1. Swagger
2. Why We Need API Documentation
3. Understanding the API Documentation
Chapter 12: Case Study - Shopping Cart APIs
Chapter Goal: A Sample application is used to demonstrate the industrial way of doing API testing, this is an equivalent to a workshop on doing API testing.No of pages: -
Sub - Topics:
1. Setting Up Application
2. Goal Setting
3. Test Environment (Docker Container)
4. Test Data Preparation
5. Agile Testing
6. Shopping Cart API End Points
7. Understanding Business Requirements
8. Manual Tests Scripts
9. Implementing Test Framework
10. Writing Test
11. Test Suite12. Execution
13. Results
14. Utilities
... weniger
Autoren-Porträt von Jagdeep Jain
Jagdeep Jain has more than 15 years of experience in Software Quality Assurance and Testing working in various product development software companies. He holds a degree in Computer Science & Engineering. He is a firm believer and advocate of test automation. He has Co-Authored Pro Apache JMeter with Sai Matam.
Bibliographische Angaben
- Autor: Jagdeep Jain
- 2022, 1st ed., XXII, 223 Seiten, Maße: 15,5 x 23,5 cm, Kartoniert (TB), Englisch
- Verlag: Springer, Berlin
- ISBN-10: 1484281411
- ISBN-13: 9781484281413
Sprache:
Englisch
Kommentar zu "Learn API Testing"
Schreiben Sie einen Kommentar zu "Learn API Testing".
Kommentar verfassen