Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Do you really want to delete this prezi?
Neither you, nor the coeditors you shared it with will be able to recover it again.
Make your likes visible on Facebook?
You can change this under Settings & Account at any time.
Performance Testing in Continuous Integration environments
Transcript of Performance Testing in Continuous Integration environments
Continuous Integration Environments
Integrating performance tests
Performance Engineer at Move Inc
1 year ago
What we did
Team structural changes
Focused on automation
Even office rearrangements!
Monitors and green lights!
Waterfall / Agile methodology
One large team of QA and Devs
Poor communication between QA, Devs and Ops
1 release every 30 ( + delays)
Partial CI - Manual builds to QA/Prod environments
Partial automated tests
Long and tense integrations
Late performance tests would delay release
Better communication among team
Less than 1 week releases
Reached continuous deployability
Visibility into build process and status
Early performance issue discovery
Teamcity Nightly Tasks
Server Side Performance Tests
1. Neoload for load generation
2. Dynatrace for troubleshooting
Client Side Performance Test
1. Cucumber and Selenium: browser side testing
2. Dynatrace : browser metric gathering
Reports and emails
Push "master" branch to performance environment
Automated integration tests
Run load test scenario
Dynatrace + Neoload
Server Side performance
Response times (Average and Median)
Number of external service calls
Dynatrace + Cucumber
Number of requests
Number of domains
Number of exceptions
Measure Front-end Performance for Not For Sale User Scenario
Measure Performance for Not for Sale Search Page
I am a new user
And I am in "Not For Sale" Landing page
And I want to measure performance for "RDC_NotForSale_Search_Page"
Given I am in "Not For Sale" SRP on "Las Vegas, NV" search
Then measure performance
Start and Stop Timers
Number of resources
Number of domains
Browser-Side performance analysis
Server-Side performance analysis
Server response time
Number of external calls
Performance Test Process
on feature complete build
This would be too late!
TOP PRODUCER® Systems
Builders Digital Experience
We are hiring!