• Claim: The easiest way to share experiences with the people that matter right now. • October 2012: Messenger hit the app store. • Rebranding: Tuenti Social Messenger | Tuenti Classic
user story / bug / task • Every commit needs a ticket (hook on repository) • Estimate. Visualize remaining time • Assign directly to developer in charge of the feature
for server and client • Jobs create on command line • tu-jenkins create-dev (unit) • tu-jenkins create-nightly (full regresion) • tu-jenkins pre-integrate <ticket-number> • Unit test every push / instant feedback for the developer • Every night unit and acceptant test execute • Email every morning to the branch owner.
and QA approved • All the API dependencies are working in live • Translations added and reviewed by QA/PM • Unit and acceptant test!! • Has latest integration merged (with blue ball)
& upload to Hockeyapp • Distribute betas internally in an easy way • Also used for collect crash reports, find bugs • Previously we had Crashlytics • Rake appstore
(Product Team) • We take latest stable (blue ball) changeset from integration and create a new Release Candidate branch • QA team makes a regression • 3 days, if something is discovered, release cancelled • Send to Apple!! • Merge back to master, integration and TAG
Login Screen ! Background: Given I launch the app And in the start screen I go to the login ! # Regular login ! @QAke(1982) Scenario: Verified new messenger user logs in and skips sync process Given a user: "myself" exists with verified: true When in the login screen I do login skipping synchronization with "myself" Then in the conversations screen I check that is the current screen