Join AT&T and reimagine the communications and technologies that connect the world. Our Consumer Technology experience team is delivering innovative and reliable technology solutions to power differentiated, simplified customer experiences. Bring your bold ideas and fearless risk-taking to redefine connectivity and transform how the world shares stories and experiences that matter. When you step into a career with AT&T, you won’t just imagine the future-you’ll create it.
Note: This role is primarily a Mobile App manual testing role, but does have automation
testing aspects.
This career step requires intermediate level experience. Responsible for the performance of any/all functions involved in the quality assurance and test execution for new and existing applications and interfaces.
Key Roles and Responsibilities:
QA Responsibilities
1. Automation Testing
• Understanding and Experience with API and UI automation tools such Appium, Selenium.
• Writing automated test cases for the various functionality defined in the sprint stories.
2. Manual Testing
• Write and execute manual test cases based on acceptance criteria
• Attach requirements to test cases
• Write defects outside of Sprint
• Conduct Test Case Reviews for sprint stories.
3. Scrum
• Attend daily Scrum
4. JIRA
• Pass/Fail Acceptance Tests
• Move user stories from In QA to appropriate swim lane
Definition of “In QA” for a Story
• All stories have acceptance criteria
o All acceptance criteria listed under the “Acceptance Tests” section
• All comps for the acceptance criteria are individually attached to the story and labeled accordingly
• Stories have NOT been updated or modified after the start of the sprint
• There is nothing missing or outstanding in the acceptance criteria
• Build is ready in the internal app store
Definition of “Done” for a Story
• All tasks completed
• All acceptance criteria met
o Tests developed, executed and passing
o Critical Defects Resolved (No Sev 1 or Sev 2)
5. Sprint Demo
• Demo sprint completed user stories that have passed acceptance criteria
6. Sprint Planning
• Help size user stories (QA should be included in story point estimates)
• Not allow user stories to be added to a sprint if QA can’t complete the work
• Not allow user stories to be added to a sprint if they are missing the following:
o All Comps individually attached to the user stories
o Acceptance criteria listed under the “Acceptance Tests” section
7. Sprint Pre-Planning
• Attend Sprint Pre-Planning
• Verify the comps for the following:
o Misspellings
o Grammatical issues
o Any conflicts with existing styling that you are aware of
8. Speak up and be persistent
Role Requirements:
• Android Studio or Eclipse for capturing logs
• Browser – Use Inspect Tool for API error codes
Education:
Preferred Bachelors of Science in Information Systems Technology, Computer Science or Engineering; Developer nanodegree; or equivalent experience.
Experience:
Typically requires 5+ years' experience. Technical Career Pathway (TCP) role.
This position requires office presence of a minimum of 5 days per week and is only located in the location(s) posted. No relocation is offered.