Technical

Question 1

Tell a bug lifecycle, process of fixing of the bug?

Answer 1

1. New (The bug is identified)
2. Assigned (The bug is reviewed by the PM, Lead, QA Lead and assigned to a dev to fix.
3. Open (Dev begins working on the bug)
4. Ready for QA (The dev finishes the bug)
5. Retest / QA (the bug is assigned to a qa team and confirms the bug is fixed)
6. Closed (the bug is fixed and the ticket of the bug is closed and resolved)

Question 2

When is it necessary to regression test?

Answer 2

Regression testing ensures that recent changes or updates to the code have not introduced new defects. Confirms that the software continues to perform correctly after modifications, such as bug fixes, enhancements, or configured changes.

Use when there is a potential breaking change to a high use feature of the application.

Question 3

What is the SDLC process?

Answer 3

It ensures that the software meets or exceeds customer expectations, is completed within time, and works effectively in the current IT infrastructure.

1. Plan
2. Requirements
3. Design
4. Implementation (Coding)
5. Testing
6. Deployment
7. Maintenance

Question 4

What is Agile Methodologies?

Answer 4

Ability to adapt to changing requirements quickly and efficientlly by welcoming change, collaboration, and continous improvement. Having a scrum team where a dedicated team focuses on specific areas of the business to efficiently collborate and hold accountability by targeting sprint deadlines. Using Kanban board to visualize, track, and manage tickets.

Question 5

Black-box vs white-box testing?

Answer 5

White Box: Testing the internal workings such as code, design docs. Includes unit testing, intergration testing, code coverage.

Black Box: Testing the external without knowing the interal structure. Includes functional, regression, uat

Question 6

Types of request (400 vs 404)

Answer 6

400 error = bad request
404 error = not found

Question 7

Verification vs Validation?

Answer 7

Verification: Confirms the software design, architecture, and implementation align with the requirements and specifications.

Validation: Confirms that the final software product fulfills the intended purpose and user needs.