Bijoya will be presenting the following session
Bijoya Chatterjee - Trust Issues with UI AutomationBijoya ChatterjeeSr. Software QA ManagerSony PlayStation
schedule 3 years agoSold Out!
UI Test Automation is notorious for stability issues. UI automation is almost synonymous with "Flaky Test". We discuss taking a proactive strategy towards test automation flakiness as opposed to a reactive approach where we look at failures and then decide the course of action. How can we in the test automation community use and develop tools that helps eliminate flakiness and also identifies flaky tests before they are not just run but even before they are merged. How do we create these tools in a service model that plugs into our Continuous Integration pipelines ?
1. What got you started/interested in Testing?
The desire to break and the passion for being a customer advocate.
2. What has been your best moment/highlight working with Appium?
My best moments with Appium has been when we have been able to write thousands of test cases and run them overnight and have confidence on our test suite to the extent that a failure always means all hands on deck.
3. What do you think is the biggest challenge faced by Mobile Testers today?
The sheer number of devices and OS versions that we need to support and test on. We rarely have the ability to test on every single device type with every single version, but there are real customers who may be using a combination that is not tested and they may be seeing defects that have crept into production.
4. What is your advice to testers, who are new to automation?
Automation does not come after development, neither does it come after manual testing. Automation is a part of the development cycle and has to be completed before any code is checked in, not after and definitely not the next sprint.
5. Tell us about the session/s you will be presenting at the conference and why did you choose those topics?
I will be presenting on "Trust Issues with UI Automation". As a tester who has had significant experience in automation and especially end to end UI automation, the most difficult part was not to write the automation, but to maintain the code and keep the tests passing so that the results could be relied on. Our team has taken on this challenge head on and come up with a service that answers some of the most important questions about automation stability and how to never have a false positive. I have chosen this session so that I can share our experience and tool set with the testing community.
6. What are some of the key takeaways from your session/s?
- Test code is like development code, it needs to be tested and it needs to be maintained.
- Testing test code should happen before it is checked in, not after the tests start failing
- Maintenance of test code should be integrated into the CI as much as possible so that we are not wasting man power analyzing test results
- If automation cannot be relied on then the basic premise on which automation is written is broken and it serves no purpose at all
7. Which are your favourite sessions at Appium Conf? (Sessions that you are looking forward to attend)
- Appium the next Generation
- Automated Solution for Non Functional Requirements (NFR) & Performance Metrics of Mobile App
- How to kill test flake in Appium
- Building Tools to Free up Exploratory testers
- Setting up Jenkins CI Pipeline using Appium tests for Android and iOS
- Run your Appium tests using Docker Android
8. Any personal message/remarks you want to share with the Testing community in India?
- Testing does not come after development, testing should be included in the development life cycle.
- Everything that can be automated should be automated, if the machine can do it why waste man power ?