Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start 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.

DeleteCancel

Performance Testing in Continuous Integration environments

Link to blog Post on this subject : http://techblog.move.com/?p=130
by

solmaz abbaspour

on 23 September 2014

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Performance Testing in Continuous Integration environments

Performance Testing in
Continuous Integration Environments

Today
Integrating performance tests
Solmaz Abbaspoursani
@s_abbaspour

Performance Engineer at Move Inc

1 year ago
What we did
Cultural shift
Team structural changes
Integrated tools
Jira
Github
Octupus Deploy
Teamcity
New Relic
Focused on automation
Even office rearrangements!
Interactive layout
Whiteboards
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
Painful deployments
...
Late performance tests would delay release
Agile
Smaller teams
Better communication among team
Less than 1 week releases
Reached continuous deployability
Visibility into build process and status
Automated tests
Reliable deployments
...
Early performance issue discovery

Teamcity Nightly Tasks
Server Side Performance Tests
Tools:
1. Neoload for load generation
2. Dynatrace for troubleshooting

Client Side Performance Test
Tools:
1. Cucumber and Selenium: browser side testing
2. Dynatrace : browser metric gathering
Reports and emails
Push "master" branch to performance environment
Run :
Unit Tests
Automated integration tests
1.
web application
Run load test scenario
Dynatrace + Neoload
Reports
2.
Metrics
Server Side performance
Response times (Average and Median)
Throughput
Error rate
Number of external service calls
Monitoring
CPU usage
Memory
Disk
Network

web application
Run test
Dynatrace + Cucumber
Reports
Metrics
Browser Metrics
Onload time
Timer duration
Number of requests
Number of domains


JS activities
Render time
Number of exceptions
Server time
...

+
@performance

Feature:
Measure Front-end Performance for Not For Sale User Scenario

Scenario:
Measure Performance for Not for Sale Search Page
Given
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
3.
4.
4.
Examples
Start and Stop Timers
Number of resources
Number of domains
Browser waterfall
Browser-Side performance analysis
Server-Side performance analysis
Server response time
Number of external calls
Performance Test Process
Performance test
on feature complete build

This would be too late!
Thank you
Solmaz Abbaspoursani
@s_abbaspour
solmaz.abbaspoursani@move.com

CAMS
Culture
Automation
Measurement
Sharing
DevOps Practices
Move.com®
realtor.com®
Moving.com
TOP PRODUCER® Systems
ListHub
TIGERLEAD
SocialBios.com
Builders Digital Experience
Featuredwebsite.com
http://careers.move.com/
We are hiring!
Full transcript