Skip to content

limehome/QA-Automation-Engineer-Challenge

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

24 Commits
 
 

Repository files navigation

Limehome challenge - QA Engineer

We appreciate your time and effort in completing the task. We believe that this task will give you an opportunity to showcase your abilities and and will help us to gain a better understanding of your approach to testing.

We understand that your time is valuable, so we kindly request that you do not spend more than 3-4 hours on the challenge.

Testing Challenge / Front End

Your task is to design and implement some scenarios for Search, Shopping (Add to cart and checkout) through product stories on https://www.limehome.com/suites?property=129&guests=1&rooms=1. Please describe a basic test strategy and implement test scenarios. Implement 3-5 test cases with the highest priority from your point of view. You should provide a detailed test report, including the test cases executed, test results, and any issues encountered during the testing process.

Testing Challenge / Back End

Your task is to write a test suite for the API endpoint https://api.limehome.com/properties/v1/public/properties/129.

  • Write a test case to verify that the API endpoint returns a 200 OK response status code. If the response status code is anything other than 200, the test should fail.
  • Write a test case to verify that the API endpoint returns the expected response body. The response body should contain details about the Limehome property with ID 129, including the property name, description, location, and other relevant details.

What we check:

  • Test coverage: Have you designed sufficient number of test cases to cover various scenarios?
  • Test script quality: Is the automation script well-organized, easy to understand, and maintainable?
  • Documentation: Did you document how to run your tests well? Is your written communication clear and easy-to-understand?

We expect you to send us a link to your code on Gitlab or Github.

Technology:

We strongly recommend Playwright, but you can use any testing methodology or tool that you prefer.

If you have any questions or feedback about the challenge, don't hesitate to reach out to us!

Good luck with the challenge! We are looking forward to your solution!

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 3

  •  
  •  
  •