QA / QA Automation
[name] asked: Tell me about transactions and ACID. How do you test parallel operations?
And when it comes specifically to Bash commands (not Git) — for example, creating a file, moving a file, etc.
Tell about the structure of the autotest project: a separate repository or a common codebase, language, build system, Java version, libraries used?
What is testing in general?
How did you create the auto-test project, and what guided your choice of tools?
What exactly did you do with databases? Please tell us more about your work with PostgreSQL.
In the [bank], what was the ratio of web to mobile testing?
What is the difference between a single angle bracket (>) and double angle brackets (>>) when writing to a file?
How did you integrate automated tests into the pipeline?
Did you lead a project from scratch, organizing automation yourself initially?
Are there any deadlines or offers? When are you ready to launch?
Why are headers needed? It seems that this information can be transmitted in the body.
What are logs? What can be found there?
What types of devices have you worked with?
What is the difference between deep copy and shallow copy, and when should each be used when preparing test data?
What practically does the use of static variables provide? What opportunity?
Test two accounts: an anonymous account up to 15,000 rubles and an identified account up to 60,000 rubles. You can buy, top up via card or SBP, and make refunds. List test cases.
What do you check when testing an API besides the response code?
Have you had experience working with framework development?
What else can be checked in a form from non-functional testing?