Connect With QA
Connect With QA
Connect With QA
-----------------------------------------------------------------------------------
------------------------------------------------------------------
Basically we have a requirements which are finalised and approved by the
stakeholders.
The developers will follow the requirements which are mentioned in the USER STORY >
Acceptance Criteria and then they will implement the code.
Assume the development team is completed the development, the next step is TEST the
developed requirements.
I will follow the UI/UX design and also i will follow the requirement details which
are added by the business analyst / product owner.
Before going to do the test exeuction, as a testing team member i have to create
the TEST CASES for each and every user story.
As a testing team member, i will start the test execution to test each and every
user story.
If i found any bug, i will raise a bug where the development team will fix that
bug.
But,
As a testing team member, if i want to raise/create a bug i have to follow some
prioritisation structure.
Whenever we tested and found any bug, we need to define what is the criticality of
the bug.
In some cases, the QA team will come to Business Analyst with the confusion state
of mind.
When the QA team will not able to decide between the stages of HIGH and MEDIUM.
The BA has to analyse the bug details and then take a priority
Is that effecting on any next workflows
will this be technical issues or functionality issue
will this be creating any criticality to the business team
Whenver the QA team created a bug as HIGH and MEDIUM the development will be fixed
asap.
Sometimes the developer will face challenges to fix the bug. So that perticular
situations the developer said, "hey team lead i need 10 days to fix it" because of
existing coding issue i have to re-arrange all the code from the begining.
At this situations, as a business analyst we have to inform the product owner about
the bug details.
If you inform to the product owner, then they will take a call for next steps or
else they will provide the directions for us to move on next steps.
Types of Testing:
-----------------------------------------------------------------------------------
------------------------------------------------------------------------
Unit testing - This will be handled by the development team when
they developed the code.(Before going to deploy in
any internal envi.)
API testing - This will be handled by the QA team when the integrations
are happend with the current application. (Data Flow)
Accessibility Testing - Its a kinda manual and automate testing where the
keyboard access is working on the application or not
After finalsing the bug fixing and the QA team will say everything is good, then as
a BA & PO we have to do the UAT to finalise the next steps.
We can try to complete the HIGH and MEDIUM but Is there any chance to give the
exceptional approval on the LOW category bugs.