Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/shrinidhimanchi/cucumber-api-automation

API Automation Using Cucumber And Axios
https://github.com/shrinidhimanchi/cucumber-api-automation

api-automation api-automation-platform api-automation-testing automation-framework axios cucumber cucumber-axios cucumber-js javascript-framework test test-automation testing

Last synced: 23 days ago
JSON representation

API Automation Using Cucumber And Axios

Host: GitHub
URL: https://github.com/shrinidhimanchi/cucumber-api-automation
Owner: shrinidhimanchi
Created: 2022-12-16T03:44:47.000Z (almost 2 years ago)
Default Branch: main
Last Pushed: 2023-01-09T20:34:23.000Z (almost 2 years ago)
Last Synced: 2024-07-30T20:52:27.557Z (4 months ago)
Topics: api-automation, api-automation-platform, api-automation-testing, automation-framework, axios, cucumber, cucumber-axios, cucumber-js, javascript-framework, test, test-automation, testing
Language: JavaScript
Homepage:
Size: 146 KB
Stars: 1
Watchers: 1
Forks: 0
Open Issues: 1
Metadata Files:
- Readme: README.md

Awesome Lists containing this project

README

# CUCUMBER API AUTOMATION

## This Project helps us in performing the automation testing of REST APIs using CucumberJs & axios

- As an automation QA Engineer, this boiler-plate project would definitely helps us in performing the automation testing of REST APIs effectively and efficiently using CucumberJs, axios and other npm libraries. In addition, since the tests are written using Cucumber, it would help any non-technical users to understand the scenario(s) built.
- This Project was built with a passion to effectively perform quick and efficient way of API tesing.
- This has helped us in solving the quick delivery to production by performing necessary validations on all of the API test(s) to ensure test deliverables are met.
- Open Source has taught many things such as share,learn and improve code through the delivery of this API automation testing.

## Table of Contents

- [Installation](#installation)
- [Usage](#usage)
- [Credits](#credits)
- [License](#license)
- [Badges](#badges)
- [Features](#features)
- [How To Contribute](#how-to-contribute)
- [Tests](#tests)

## Installation

Please run the below commands sequentially from the current/present working directory of the cloned project to download all the dependencies required for the project.

```
npm install
npm run startUpScript
npm run executeShellScript
```

## Usage

We make use of `NODE_ENV` Global variable to execute the tests based on the choice of the environment.

In general, we could categorise environment as below -
- development(environment used for developmental activities)
- testing(environment used for conducting either `System Testing` OR `System Integration Testing`)
- production(for production activities such as business acceptance testing OR business verification testing)

Whenever we want to run the tests, we use `NODE_ENV` with the value of either `development` OR `testing` OR `production`

For our testing activities, we would make use of `testing`. (i.e, `NODE_ENV=testing`)

```
NODE_ENV=testing npm run cucumber-petStoreTest
```
Alternatively, we can make use of shell-script to run the tests!

Hurray!!! Yay!!!

Please execute the below command from either `terminal` or `Iterm`

```
./api-tests/cli/runAcceptanceTest.sh
```

When we run the above command, it would prompt us to select from the displayed choice of list.

- Select `3` for now to execute the test(i.e, Press the numeric `3` on the keyboard to proceed further and press `enter` or `return` keyword).
- Select the appropriate feature to execute the tests(i.e, Press `1` for now since the `cucumber-petStoreTest` used on the feature file is `petStoreTest`) and press `enter` or `return` keyword.
- It would show us the fully qualified command on the `terminal` followed by running the tests.

Once the tests are run successfully, reports would be generated under `output` directory(i.e, `api-tests/output/`)

-- An `.html` file automatically pops up in a browser on `Mac` once the above command gets executed.

We have 2 types of `.html` report(s) generated(as mentioned below)

- Cucumber's default html report(i.e, Cucumber generates the default HTML report under the directory(`api-tests/output`) with the filename set to `inBuiltReport.html` as specified under our `cucumber.js` config on the root directory of the project.

- Using the npm module `multiple-cucumber-html-reporter` that gives the beautify HTML report under the directory(`api-tests/output/multiple_cucumber_report/`) with the filename set to `index.html`.(Kudos to its creators: `wswebcreation` for coming up with one of the amazing plugin to show the enriched information of cucumber tests)

Below folder hierarchy is used in building the project.

```
api-test-automation
├── api-tests
| ├── cli
| | ├── cliParser.js
| | └── runAcceptanceTest.sh
| ├── config
| | ├── development
| | | └── development.json
| | ├── production
| | | └── production.json
| | ├── testing
| | | └── testing.json
| | └── ...
| ├── cucumber-report
| | ├── report.js
| ├── feature
| | ├── petStore.feature
| | └── ...
| ├── output
| | ├── multiple_cuc
| | | ├── index.html
| | | └── ...
| | ├── inBuiltReport.html
| | ├── messages.ndjson
| | ├── output.json
| | ├── progress.txt
| | ├── rerun.txt
| | ├── summary
| | ├── usage.ndjson
| | └── usage.txt
| ├── prerequisities
| | └── startUpScript.js
| ├── requests
| | ├── testData
| | | ├── testData-development
| | | | ├──
| | | | └── ...
| | | ├── testData-production
| | | | ├──
| | | | └── ...
| | | ├── testData-testing
| | | | ├──
| | | | └── ...
| | └── requestBody.json
| ├── step_definitions
| | ├── support
| | | ├── baseWorld.js
| | | ├── dataStore.js
| | | ├── envConfiguration.js
| | | ├── parseResponse.js
| | ├── step_definitions.js
| | └── ...
├── cucumber.js
├── customFormat.js
├── package.json
├── README.md
└── ... # This file helps us in validating `NODE_ENV` is a mandatory input while running the tests via shell script. # This shell script helps us in running the test without having to type the fully qualified command on terminal. # This directory contains all the properties required for executing the test(s) in `DEV` environment. # This `json` file will have the user defined properties required for executing the test in `DEV` environment. # This file contains all the properties required for executing the test(s) in `PROD` environment. # This `json` file will have the user defined properties required for executing the test in `PROD` environment. # This file contains all the properties required for executing the test(s) in `TEST` environment. # This `json` file will have the user defined properties required for executing the test in `TEST` environment. # This file contanins all the options required for generating html report for the npm library `multiple-cucumber-html-reporter` # This directory contains the list of `.feature` files required for executing the cucumber tests based on tags. umber_report # This `.html` file contains the viewable html report generated by npm plugin `multiple-cucumber-html-reporter` # This `.html` file contains the viewable html report generated by cucumber's default html report # This `.ndjson` file contains the artefact of cucumber execution in `ndjson` format. # This `.json` file is the artefact of the `cucumber` feature execution. # This text file contains the progress of the cucumber execution. # This text file contains the re-run result of the cucumber execution. # This text file contains the summary of the cucumber execution. # This `.ndjson` file contains the artefact of cucumber execution in `ndjson` format. # This text file contains the usage of `step-definition` along with the `pattern` and `location` of it. # This file contains the required functions to create `output` directory along with the required `.json` file. # This directory contains the collection of all input test-data required to run the given tests. # This directory contains the collection of `.json` files required for executing `development` env tests. testData-development.json # This file contains the array of JSON Objects(i.e, collection of scenario data) # This directory contains the collection of `.json` files required for executing `production` env tests. testData-production.json # This file contains the array of JSON Objects(i.e, collection of scenario data) # This directory contains the collection of `.json` files required for executing `testing` env tests. testData-testing.json # This file contains the array of JSON Objects(i.e, collection of scenario data) # This `.json` file contains the list of input payload required for `PATCH`, `PUT` & `POST` requests. # This class file extends the `World` class of `cucumber` along with the required reusable functions. # This file contains the list of reusable functions required for fetching the input data and header functions. # This file reads the `name-value` pairs of `.json` file(if exists) from the `config` directory. # This file contains the list of reusable functions required for playing with the response returned from server. # This file contains the collection of `step-definitions` required for executing the feature file. # This file contains the required configurations to execute our cucumber tests. # This file gets executed when `customReport` is choosen for reporting the artefacts. # This file lists out the required dependencies along with the essential node scripts required for the project. # This file contains the README instructions to setup the project and execute the tests.

```

## Credits

A Big Thanks to the following open source libraries(along with tutorials) which helped in building this project.

- https://github.com/wswebcreation/multiple-cucumber-html-reporter
- https://www.npmjs.com/package/axios
- https://www.npmjs.com/package/@cucumber/cucumber

## License

MIT 🏆

---

## Badges

![badmath](https://img.shields.io/github/languages/top/lernantino/badmath)

## Features

- Lightweight automation framework for executing API tests using `cucumber-js`
- Reusable javascript function(s) for better readability of the code.
- Use `Visual Studio Code` for better traceability.

## How to Contribute

- Create a branch out of `main` or `master`.
- Make required changes to the code and raise a pull request.
- Once pull request is approved, update the contributors sections in `package.json` file for better traceability.

## Tests

If any code changes are applied ensure all the existing feature test(s) are working as expected.