Functional Testing and Continuous Delivery at

Yahoo! MailNeil Manvar

Front-End Developer

About Me

- 2 years with Yahoo! Mail- Bachelors in Computer Science &

Engineering from UC Davis.- Hobbies include UFC/MMA, cycling, and

video games.- CS Interests include in-browser functional

testing and exploring new FE technologies

Role of Browser Testing in Mail

- No more dedicated QA’s- Need to make sure Mail works on various

different configurations- Going towards CD Model

- need automated tests to certify product

Ycuke - Functional Testing Framework

- Cucumber- Watir-Webdriver- Page-Object- Parallel_tests- Saucelabs (get a free trial here!)

Sample Testcase - Feature file

Scenario: Composing a new message and saving as draft Given I am logged in to Yahoo! Mail as User1 And I open compose And I fill out the subject field with “someRandomContent” And I fill out the email message body with “someBodyContent” And I save draft by pressing Control + S Then I should see the save draft confirmation notification

Sample Testcase - Step Definition

step_definitions/Compose_steps.rb:

And /^I fill out the subject field with “(.*)”$/ do | content |on_page Compose do | page |

page.subject_field.when_present.set(content)end

end

Sample Testcase - Page Object

page_objects/Compose_page.rb

class Compose include PageObject

...def subject_field

@browser.text_field(:id => “to-field”)end

...end

Complications

Parallelism- Account Problems- Abuse / Anti-Spam

Continuous Delivery Pipeline

1. Developer submits pull requests- Unit tests are run against pull request.2. Code is reviewed and merged in if PR build

passes.- Unit and Functional Tests are run3. Code is pushed to test servers, and pushed

to prod after “integration” functional tests passes

Trying to run functional tests on Pull Request build.

Challenge: Will get flagged as abusive / spam since we have > 20 pull requests

Solution:Mock backend (record and replay)

Q & A

Try Sauce Labs free! Click here and get a free account!