Skip to content

Instantly share code, notes, and snippets.

@alexanderkustov
Last active May 21, 2024 13:34
Show Gist options
  • Select an option

  • Save alexanderkustov/62c04e4b750ca753b68ec34485d40a6b to your computer and use it in GitHub Desktop.

Select an option

Save alexanderkustov/62c04e4b750ca753b68ec34485d40a6b to your computer and use it in GitHub Desktop.

Thanks for your interest in applying for the position of QA engineer with Axate. We have received an unexpectedly large number of applicants. To help us make sure you're the right fit for Axate (and that Axate is the right fit for you!) please answer the following questions. We don't require lengthy answers - we are looking to understand your approach.

Approach to QA Testing in Modern Web Applications

  • Can you describe your strategy for QA testing in modern web applications (react/typescript)?
  • How would you keep testing and the code independent from the codebase and clearly maintainable?
  • What methodologies do you use, and how do you ensure that test coverage is thorough and that the tests remain maintainable?

Testing the User Journey on Axate.com:

  • The link below contains a mock up of the user registration journey. In this journey a user signs up, inputs payment information, and pays. How would you test this process? Which strategies and tools would you employ, and why?

You can see the registration process here - start at the far left of the screen

React Component Testing:

  • You need to test a React component that shows a user's profile information retrieved from a Rails API. How would you go about testing this component, considering both unit and integration tests?
  • What tools and libraries would you use?"

Visual Regression Testing:

  • When rolling out new changes, how do you ensure there are no unintended visual discrepancies between the current deployment and previous ones?
  • What tools and techniques would you use to automate visual regression

Testing GitHub Branches:

  • How do you approach testing various GitHub branches before integrating them into the main branch?
  • What steps do you take to ensure that changes in feature branches do not disrupt existing functionality or introduce bugs?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment