Naveen Khunteta
Test Architect
Naveen Automation Labs
location_on India
Member since 5 years
Share
Naveen Khunteta
Specialises In
- An Automation SDET Architect, experienced in Automation, Functional/Non Functional (Security & Performance Testing), DataBase, Backend API, Mobile Testing & DevOps.
- Ability to Manage Multiple Automation Projects on Multiple Automation Tools, Manage the Complete Automation phases from Initiating, Planning, Executing, Controlling, and Reporting.
- Ability to Establish and Manage Testing Centre of Excellence (TCoE) - QA Community and create innovative efficient Testing solutions, Automation Solutions and Automation Frameworks to Accelerate delivery.
Programming Skills:
Strong hold on Data Structure & Algorithm, Java, Python, JavaScript, VB, SQL, Shell Script
Automation Framework & DevOps Skills:
Data Driven, Key Word, Hybrid, Page Object Model, Selenium WebDriver/GRID, AutoIT, SIKULI, Groovy, TDD (JUNIT/TestNg), BDD (Cucumber-JVM, JBehave), BDD Serenity, SVN/GIT, MAVEN/ANT, Jenkins, SauceLabs, BrowserStack, Docker, AWS
JavaScript Tools: Jasmine, AngularJS, Protractor, Grunt, Mocha, Cypress, Taiko, Gauge
AI Tools: AppliTools, Testim.io
Mobile Test Automation:
iOS & Android devices: Native/Hybrid/Browser apps testing using Appium, BrowserMobProxy, Charles Proxy
API (Backend) WebServices Automation:
SOAP, REST, HttpClient, Gson, SimpleJson, Jackson, Jersey Client, REST Assured, SOAP UI, JSON, XML, JMETER, Swagger, Marshelling, Un-Marshelling, Mockito, WireMock, POSTMAN, NEWMAN, CURL
Performance Testing: Jmeter, LoadRunner, GATLING
Performance Monitoring/Alert: Grafana, Medusa, GrayLog, Kibana, PagerDuty
Dev Ops: Maven, Jenkins, Docker/Hub, Arquillian Cube
Code Coverage: JaCoCo, Cobertura, SonarQube
Project/Test management Tools: JIRA, Rally, HP-QC/ALM, Test Rail, Agile
-
keyboard_arrow_down
Best Practices to implement the test automation framework starting from Design - To -> Infrastructure - To -> Execution.
45 Mins
Talk
Intermediate
Best Practices - How to get the best 'Return ON Investment' (ROI) from your Test Automation.
This has been observed that, most of the test frameworks wont be able to survive due to lack of expertise, no maintenance, no best practices being followed, and finally your test automation will be dead after few months, and there is no "Return ON Investment" from this. This is the most common problem, most of the companies are struggling and finally back to square to the Manual testing.
My proposal : HOW to leverage your test automation in terms of best practices, best ROI, and how to adopt best automation culture in your organisation.
I strongly propose some of the important points/suggestions to achieve this in your Organisation/Team.
1. Test Automation Practices:
- Design Patterns (Web/Mobile/API)
- What to Automate/Not to Automate
2. Common Automation Frameworks at Org Level:
- How to design Generic Utilities, Libraries and different Components, which can be suitable for all the teams in the same Org.
- Best practices to design your Tests (Automation).
- Common Design Patterns
- Common application level and Page libraries
- Best Practices to use Assertions in your Tests (How and What to write for assertions). Most of the people don't write proper assertions and this is making your test unreliable and no defects found during execution.
3. Inclusion of API/Backend libraries in your UI test automation as an external Maven/Gradle Dependencies to avoid un-necessary tasks, some of the important points to be considered here:
- User Creation from APIs (No need to automate user creation from web/app for all the test cases)
- API tests are stabled most of the time
- API calls takes lesser time as compared to web, hence include API calls in your UI/App framework to save time.
- Less flaky test
4. Best Code Review Process (Do not merge your code into Master without proper Code Review)
- Implement PR (PULL Request) Process
- Static Code Analysis using SonarQube, Cobertura, JACOCO etc..
- Get the benefits of Best Test Automation Quality Matrices
- Sometimes, Manual (Functional Tester) should review your code (Assertion, test steps and use cases) to get the best coverage
5. Quality is A Team responsibility:
- Developers, POs, Manual QEs and Automation engineers should be included to get an overview of test automation coverage.
6. Maintenance of the Frameworks
- After couple of months, it should not make your life miserable if you don't maintain your libraries and framework properly.
- Do not use Hard Coded values, make it simple and Generic.
7. Infrastructure Setup for Test Design and Test Execution:
- Proper Browser - OS lab setup
- Proper Mobile Labs setup with different Devices - IOT, iOS, Android, iPad, Tablets
- Proper CI - CD common configuration using Jenkins, Dev Ops, AWS, Docker and Cloud setup
- Handling multiple Docker nodes using Kubernates (use of Selenoid, GRID on Cloud)
-
No more submissions exist.
