Automation and parallel testing practice after the learning and basic understanding of Selenium Webdriver, WebDriverIO and Cucumber.

• UI Automation
  • Log into the site
  • Sort the items (Lowest Price sort)
  • Add two or more items to the shopping cart
  • Visit the shopping cart
  • Assert that the items that you added are in the cart
  • Remove an item and then continue shopping
  • Add another item
  • Checkout
  • Assert you are purchasing the correct items
  • Assert the total price
  • Finish checkout
• API Automation
  • Make GET, POST, PUT, and DELETE calls
  • Set headers for a request
  • Set the body for a request
  • Assert the response from a request
  • Use the response from one call in the request for another

Mocha, Chai, Supertest, WebDriverIO, Cucumber

The test functionality includes:

• UI
  • Login
    • User may login with registered credentials
  • Inventory/Cart
    • User may sort inventory items
    • User may add items to shopping cart
    • User may remove items from shopping cart
    • User may visit the shopping cart
  • Checkout
    • User may confirm items added
    • User may confirm total amount
    • User may checkout
• API
  • User may request a post
  • User may create a post
  • User may patch a post
  • User may delete a post

• ui-test
  • features
    • cart.feature
    • checkout.feature
    • DEMO.feature
    • inventory.feature
    • login.feature
  • step-definitions
    • cart
      • given.js
      • then.js
      • when.js
    • checkout
      • then.js
      • when.js
    • inventory
      • then.js
    • login
      • given.js
      • when.js
    • reusable
      • given.js
      • then.js
      • when.js
  • support
    • actions.js

There does not seem to be a generally approved standard for directory structure in tests, and is more dependent on the team's choice. For this reason, I found it more convenient to keep a When/Given/Then structure for scalability purposes.

• api-test
  • tests
    • api.test.js
  • test-setup.js

Clone the repository to your local computer

git clone https://github.com/dionisggr/saucedemo.git

Use the package manager npm to install dependencies:

npm install

Don't forget to audix fixes if needed:

npm audit fix

Run the UI automation tests in parallel (Chrome & Firefox):

npx wdio wdio.conf.js

Run the API automation tests:

npm test

Tests run in instances of 5 for performance consideration in the user-end when running the tests.

You may change the maximum instances 10 (maximum amount of tests) or higher, as your machine allows.

In wdio.conf.js:

...

exclude: [
  // 'path/to/excluded/files'
],

maxInstances: 5,   // Change to 10, or your preference

capabilities:[{
  ...
}]

...