JIRA Flashcards
Both ROLLBACK and COMMIT are Transaction Control Commands (TCC) with distinct purposes: COMMIT is employed to permanently save changes made to the server, making them a permanent part of the database. ROLLBACK, is used to undo changes, reverting to the previous state, discarding any modifications made during the current transaction.
Can you explain what JIRA is and its relevance in the QA process?
It is used by software and commonly for development, and QA teams for tracking issues and projects, helps to manage defects, stories, tasks, and other project-related items. JIRA is very important for recording defects, monitoring the progress, connecting them to requirements or user stories, and confirming resolution before releases.
How do you prioritize defects in JIRA?
We use the “priority” field to prioritize the defects, with options such as Blocker, Critical, Major, Minor, etc. To choose which one the select is based on the defect’s impact on the application, business severity, and the urgency for resolution.
Explain how you would use JIRA’s comment and attachment features during defect logging.
Comments useful for adding extra details, updates, or explanations about the defect. Attachments plays important role for providing evidence for the defect, such as screenshots, logs, or videos for repeating the issue.
How do you ensure that developers understand the defects you’ve logged in JIRA?
I always create clear and brief defect titles with detailed descriptions, including steps to reproduce, expected and actual results. also, I attach relevant screenshots or videos and direct communication is also can be choose when needed to ensure clarity.
What JIRA add-ons or plugins have you used in relation to QA processes?
I’ve used Zephyr for test management, and Confluence for documentation integration.
How do you handle regression defects in JIRA?
for easy filtering it can be labeled or tagged as “regression”. Also, they can be linked to the original defect to maintain traceability.
How do you manage the test execution status in JIRA?
With test management tools integrated into JIRA, like Zephyr, it can execute test cases directly within JIRA and update their statuses as “Pass”, “Fail”, “Blocked”, etc.
Describe how you’d use JIRA in a Continuous Integra-tion/Continuous Deployment (CI/CD) environment
JIRA integration with CI/CD tools like Jenkins enables automatic updates on build status, triggers test cases after deployment, and automatically logs defects if tests fail.
Explain the difference between an Epic, Story, and Task in JIRA from a testing perspective.
Epic is a large feature or functionality to be tested. Story is a smaller, user-focused part of functionality within that Epic. Task might be a specific test activity or preparation related to Story, such as setting up test data or creating a specific test script.
What is an epic?
An epic is a large user story that cannot be delivered as defined within a single Sprint. It is large enough that it can be split into smaller user stories.
What’s a user story?
User stories are short and simple descriptions of what a system should do, written from the user or customer’s viewpoint. user stories also called requirements.
How do you handle non-reproducible defects in JIRA?
If it is hard to reproduce every time, I give as much detail as possible - like where it happened, the exact steps, and any attachments related to it. If it is still non-reproducible, I would say it’s not reproducible, but I’d keep a record just in case it happens again.
How do you manage test data within JIRA?
for that integration with tools like Confluence or plugins is used for documenting and tracking test data. Custom fields or links to external test data repositories can also be added to relevant issues, improving the overall capability for test data management.
Describe how you would handle versioning of defects when multiple releases are being tracked in JIRA.
In JIRA, the “Fix Version/s” field helps track which release will address a defect. If a defect affects or it is fixed in multiple releases, I’d use this field to specify those versions.
How would you handle a scenario where a developer disagrees with a defect you logged in JIRA?
Communication is always key. I’d first confirm that the defect description is clear and has all the necessary details. Then, I’d set up a meeting or discussion with the developer, possibly do a live reproduction of the defect. If there’s still disagreement, It could be taken to a team leader or manager to find a solution.
