Steerbridge Flashcards
Talk about developing and executing test plans and test cases.
First thing is to always understand the requirements and specifications of a project. work closely with team members and product managers to make sure there is no ambiguities.
Designing a good test plan involves outlining the scope, objectives, test types, and deliverables for test completion and success.
A good test case involves being very detail orientated and based off the test plan. You’ll want a unique id, pre conditions, steps to reproduce, data, and expected vs actual results with a pass/ fail status.
And for executing I systematically run each test case while documenting the results meticulously, logging any defects I find along the way in detail to share with developers.
talk about Identifying, documenting, and tracking bugs and defects.
During testing phase I pay close attention to any odd behavior, inconsistencies, and any deviations from expected results.
once a defect is identified, I first thing I do is try to reproduce the bug at least three times and in different scenarios to confirm its not restricted to a specific environment.
I then want to document and report to a developer to get worked on immediately and will also work closely with them to solve the issue. I use a bug tracking system like Jira to document and track my findings.
Once the bug has been fixed I’ll retest to verify the issue has been resolved and perform a regression test to ensure no new defects were introduced during the process.
Experience with Postman
Recently, we introduced a new Order Management API to handle order creation, updates, and cancellations.
Create Order: I tested the POST /orders endpoint with valid order data and verified that the API returned a 200 Created status with the correct order details in the response. I also tested edge cases, such as placing orders with maximum allowed items.
Update Order: I tested the PUT /orders/{orderId} endpoint to update order details, ensuring that only valid updates were accepted and reflected correctly in the database.
Cancel Order: I tested the DELETE /orders/{orderId} endpoint to ensure that orders could be canceled and appropriate status codes (e.g., 204 No Content) were returned.
Experience with Selenium
In my current role in the e-commerce department, automation testing plays a critical role in ensuring the quality and reliability of our software. We use Selenium for browser-based end-to-end testing, which allows us to automate user interactions with the website. For example we automate end to end user transactions from browsing products to complete purchases and automating the entire checkout process.
We use automated regression tests to ensure new code does not introduce any new bugs and re-running a suite of automated tests on the entire application after a new feature is added to ensure that existing features still work as expected.
Collaborate with cross-functional teams to ensure quality throughout the software
development lifecycle.
The best way to start collaborating with teams is right from the beginning , this ensures theres no ambiguities and everyone is on the same page about the requirements and specifications about the project.
I firmly believe in open and clear communication, to not be afraid to ask questions, and discussing topics such as what can be tested manually vs what can be automated.
Continuous feedback is important for promptly resolving issues.