Test Engineering - Life of a TE in BBM

As one of the most growing engineering teams in BBM, test engineering team re-introduces about who they are, what they are doing on each release cycle and some other interesting facts about themselves.

Transcript

1. Test Engineering Life of a TE in BBM
2. Outline - Introduction to Testing - TE Cycle - Interesting facts - Challenges
5. Introduction to Testing • What is software testing? A process to identify bugs and to ensure the software matches with requirement, manually or using automated tools. • Why is it important? Save time and money by reducing software development and maintenance costs. Ensure a good user experience. • What do we do in BBM? Feature/Bug Testing Smoke Sanity Regression Targeted
6. TE Cycle Requirement Analysis Test Planning Test Case Development Test Execution Test Closure IPM Retro Updated list of high level test cases. Manual / automated Master, internal, external beta, gold candidate. Finished features, bugs Updated list of (manual) detailed test case. Automation test cases (Robot Framework) Results for smoke, sanity, regression and/or targeted testing. Bug triage (updated) Feature Spec Doc PT feature / bug stories
7. Interesting facts 1. Respin 2. Intermittent bugs 3. We also code! 4. Image comparison 5. Not 100% automation 6. Config our own CI 7. Using emulator
8. In automation testing: 1. Different result between local and CI 2. Element identifiers can be differ per release 3. Integration test for multiple platforms, for example mobile and desktop 4. Keep the test automation stable Challenges