Straiv | QA Assesment Task

📜 About

Stariv assessment task is a small task given to check the manual and automation skill ability of a QA engineer. This repository contains the automated tests for UserLogin and UserRegistration functionality for the website Automation Exercise using Cypress.

Source Code Structure

STRAIV_ASSESMENT_TASK

|-- cypress								

	|-- downloads

	|-- e2e
		|-- checkoutProcess.cy.js			# Automation script main file for checkout-process module
		|-- productSearch.cy.js				# Automation script main file for product-search module
		|-- userLogin.cy.js					# Automation script main file for user-login module
		|-- userRegistration.cy.js			# Automation script main file for user-registration module
	
  |-- fixtures
	
  |-- support
		|-- checkoutHelpers.js				# Reusuable helper functions for the checkout-process module
		|-- productSearchHelpers.js			# Reusuable helper functions for the product-search module
		|-- userLoginHelpers.js				# Reusuable helper functions for the user-login module
		|-- userRegistrationHelpers.js		# Reusuable helper functions for the user-registration module
		|-- e2e.js							# Reusuable helper functions for the commands module
		|-- command.js						# Custom command creation module 
		|-- commonHelpers.js				# Reusuable and common helper functions which is used by the application

|-- Documents
	|-- Bug Reports.docx					# Bug Report document
	|-- TestCases.xlsx						# All relevant test cases document
	|-- TestPlan.docx						# Test Plan with all details document
	|-- Straiv Final Testing Document.docx				# Complete testing document

|-- .gitignore				
|-- automationframework.md		
|-- cypress.config.js						# Cypress configurations file
|-- package.json							# Needed packages to run the application
|-- package-lock.json							
|-- Readme.md
-	

Cypress vs Playwright

There are couple of good automation framework which serve our purpose. But here for our example we have choosen cypress to perform our automation tasks. There are couple of reasons as to why cypress was choosen. Inorder to find out why cypress was choosen instead of other frameworks, one can please refer to Cypress VS Playwright documentation for more information.

📟 Recommended Setup

Prerequisite:

• VSCode
• Node

⚙ Project Setup

Setup

• Clone the Git repository

  git clone https://github.com/MeghaVernekar23/straiv_assesment_task.git

• Navigate to the project directory:

  cd straiv_assesment_task

• Install all necessary packages:

  npm install

• Run the development server:

  npx cypress open

Opening Cypress for the First Time?

Once the dependencies/packages are installed, you can open the Cypress test runner

• Open cypress runner:

  npx cypress open

  This will open the Cypress Test Runner, which allows you to select the browser, configure your testing environment, and run your test files.

• Choosing Options in Cypress for the First Time: When you run Cypress for the first time, you'll see a welcome screen. Follow these steps:

  • Choose a Testing Type:
    

    • Select E2E Testing (End-to-End Testing).
      

  • Select a Browser:
    Cypress supports multiple browsers. For the first run, it’s recommended to use Chrome or Edge, as these browsers have the best compatibility with Cypress. You can choose:
    

    • Chrome: Ideal for most use cases.
      
    • Electron:
      
    • Edge:
      

  If you want to run the tests in headless mode (without the browser UI), you can choose this option from the command line:

  npx cypress run --browser chrome

Running Your First Test

Once the browser is selected, Cypress will show the list of available test files. Click on a test file (e.g., tests/e2e/userLogin.cy.js) to run it in the selected browser.

Cypress will automatically execute the test and show real-time results in the test runner. You can watch each test step with time travel, which allows you to see exactly what happened at each step.

Contact

If there are any questions please feel free to contact
Name: Megha Vernekar
Email: [email protected]