This document discusses modern functional testing and DevOps. It provides an overview of the speaker including their experience and role. It then discusses QA team structures, timelines versus tasks, and how QA needs to adapt to keep up with faster release cycles. Various testing approaches are presented including automation, manual testing, different test environments, API and integration testing. The importance of automation, regression testing and tracking work is emphasized to support continuous delivery.
2. About me
▪ Senior Engineer Software Salesforce
▪ QA Group Manager at HP Software
▪ 11 Years of experience in testing
▪ Blogger and thought leader in QA
▪ Volunteering to help Arabs in Hi-Tech
2
14. Dev Commit CI Run Micro Service
Tests
• Micro service API coverage
• Smoke level (CRUD)
Upload
To Registry
Dev Env
Deployment
QA Env
Deployment
QA Automation
Stable
• E2E Using REST
• UI Automation
• Replay LeanFT Scripts
• Remote tests:
UFT/LFT/Selenium
• Daily
SaaS Non-Prod
• Running Integration tests
• Working on a real SaaS ENV
• Most of the QA coverage is
done here
SaaS staging
Production
Test Environment
27. Automation Microservices
27
NEW MS Docker Image
Upload to
Registry
Build new MS
Report
TestsExecution
Results
SRF-Green
Deployment
Abort Uploading
new image to Registry
ContinuousDelivery
API TestsMicroservice
Mocks
+
Docker Testing Container
api.tests.common
module
NEXUS Import
Notify
Developer
General Test API’s
28. API Testing
SRF
API Integration
Tests
UI Tests
Utilities and Tools
Exam
Framework Users
Methods for expanding the
framework capabilities
Example
Request handler for parsing
the response, and catch and
log errors
REST end points organized by
SRF pages for easy view and
search
Example
SRF.automation.getMobileDevi
ces
Request loader tool for
tracing 502 errors
Data population at the
beginning of a test run
Complete REST end points
testing to ensure correct
response and valid data
API Framework
This what will happen when is not in shape to run fast
When a test fail in CI/CD (Jenkins) the branch of Release will be blocked, in this slide we see that it is closed because tests failed, in the next picture we will see when it is opened after the bug was fixed and automation passed successfully.
Real example from my team, Olga is a DevTest in my team, she send a notification mail to Developers saying that branch was closed, and a defect was opened because a automatic test failed (automation find a real defect)
I am sure that a developer pushed code and damaged some other parts in the product.
Then we see a mail from Developer his name is Ilan.
Unstable automation should be removed
Using SRF
Can we test our APP’s with all devices?
Exploratory Web
Exploratory mobile
Automation
Unstable automation should be removed
Using SRF
Who should test tools and what about automation
Example for MC / LFT / UFT
Track daily work to make sure Agile is done as expected
Agile doesn’t work out of the box, we should keep tracking
Unstable automation should be removed
Regression plan how it was before and what we do today with Octane
Who we do regression today
Automation VS Manual
שינוי החשיבה שלנו בעדיפות על פני הטכנולוגיה. כאשר נעבוד ביחד, נצליח
