1. Shaping yourself to SDET from AT Sriram Angajala

2. ABOUT this MEETUP Group
EDIT IN GOOGLE SLIDES
Click on the button under the presentation preview that says "Use as Google Slides Theme".
You will get a copy of this document on your Google Drive and will be able to edit, add or delete slides.
You have to be signed in to your Google account.
EDIT IN POWERPOINT®
Click on the button under the presentation preview that says "Download as PowerPoint template". You will get a .pptx file that you can edit in PowerPoint.
Remember to download and install the fonts used in this presentation (you’ll find the links to the font files needed in the Presentation design slide)

3. Welcome to the first LONDON SDETs Meetup
Lets start this with a Smile and Claps

4. Formally this meetup was called ‘East London Testers’
History
Formally this meetup was called ‘East London Testers’
First Meetup was on “Mobile testing in isolation”
Second Meetup was on “Visual Regression Testing”

5. Speaker in TEST CONFERENCE Experience in BBC, TFL, VISA EUROPE, IBM
About organizer
SRIRAM ANGAJALA
Lead SDET in Eurostar
Speaker in TEST CONFERENCE
Experience in BBC, TFL, VISA EUROPE, IBM

6. Speakers Ayyappa Swami – Automation QA at Portal Tech - Sony
Srikanth Madduri – SDET at Eurostar
Surya – SDET at Thomson Reuters

7. Sponsers
our office

8. What is this MEETUP will do over period of time

9. Talk about most important topics about SDET*
Learn technologies and Tools
Share experiences about SDET
Change is Changing and hard to keep up the pace SO …
Lets share and keep up the pace

10. Why does companies looking for in SDET
Improve Quality – More Automated Tests and more time for exploratory testing
Faster Deployment – Add more business value quickly
QA’s can work independently with out Devops etc
How will it help for a typical Automation tester to grow as SDET
Learn More about Development Process
Control whole testing from code and unit testing level
Isolated testing to increase coverage and reduce false positive
Keep up with the expectations

11. How ever automation is run only on QA Merge - Integrated
CASE STUDY
A gaming company follows the environments as Dev Alpha, QA Alpha and QA Merge for testing at various levels.
How ever automation is run only on QA Merge - Integrated

12. Inbound – Calls from 3rd parties into the System
API Testing
API testing is done for
Inbound – Calls from 3rd parties into the System
Outbound – Calls made from System to 3rd Parties from UI

13. 1. Maintaining many environments making complicated 2
1. Maintaining many environments making complicated 2. Automation test coverage not 100% 3. Automation is too late in the process 4. Mostly API tests are manual test 5. Manual testing done in individual work packages 6. Waiting for deployments .

14. Our GIT flow / Automation Process
Yellow
Blue
Red

15. OUR - Application Folder
Module 1 Application Folder
Fronted Application Folder
App Source Code
Main Source Code
Unit Test Folder
Integration Test Folder
Bdd Tests Folder
Mock Responses Folder
Load Testing Folder
Security Testing Folder
Backend Application Folder

16. Involve more into development process
Make every component Testable and improve quality
Reduce Dependency and reduce release cycles
Faster deployments
Feature level testing
Isolated testing using stub
Involve more into development process
WHY

17. Involve more into development process
Read the Readme documents
See the architecture documents
Download the source code
Run build locally
Involve more into development process
How

18. Involve more into development process
Understand the stack
Cut the pieces
Check unit test coverage – add more if required
Identify integration test coverage and add more if required
Stubs
Create functional tests in development folder
Run the tests in isolation
If defects found identify the issues
Logs
Dataflow
Translations
3rd Party
Fix if u can
Add tests for missing tests
Involve in PR Code review
Involve more into development process
Day to Day

19. Testing Types
Functional tests
End to end Tests
API testing
Load testing
Security testing
Visual testing

20. Involve more into development process
What to learn then and improve skills
Tools
API testing tools
Frontend testing tools
Github
Devops – deployments and environments
More Tools
Load testing
Security testing
Visual testing
Involve more into development process
Finally

21. Any questions? Find me at sriram.angajala@gmail.com
Thanks!
Any questions?
Find me at