12
Running agile, testable content deployments from start to finish Emma Armstrong @EmmaATester

Running agile testable content deployments from start to finish slideshare

Embed Size (px)

DESCRIPTION

Our content management tool may be a source control system, but Deployment Manager is a web app like any other, and regularly deploying content is core to how we work. Being an Agile team, we’ve had to work hard to automate a large amount of our testing across different browsers (using Selenium), and have put systems in place to make it possible to release code and content together - with a minimum of risk and headache - on a weekly basis. Everything we’ve learned applies to any web application CMS, and this session will look at some of the release mechanisms we’ve put in place - how we’ve implemented them, the hard choices we’ve made to get to where we are, and how the relationship between developers and testers has been essential to make this possible.

Citation preview

Page 1: Running agile testable content deployments from start to finish slideshare

Running agile, testable content deployments from start to finish

Emma Armstrong

@EmmaATester

Page 2: Running agile testable content deployments from start to finish slideshare

Continuous Delivery

The aim to rapidly and reliably release to production.

Page 3: Running agile testable content deployments from start to finish slideshare

Frequent Releases

Deliver user value

First to market

Feedback

Page 4: Running agile testable content deployments from start to finish slideshare

Cost of releasing

How long does it take to release?

What is the probability and cost of

mistakes?

Is the right person available?

What was tested prior to release?

Can we rollback?

Page 5: Running agile testable content deployments from start to finish slideshare

Process

1. Write your content2. Add your content to CMS3. Deploy your content

What is missing?

Page 6: Running agile testable content deployments from start to finish slideshare

Demo

Page 7: Running agile testable content deployments from start to finish slideshare

Testing

• What to test• Are all the pages there?• Is it the correct version of the page?

• What to use• NUnit• Selenium

Page 8: Running agile testable content deployments from start to finish slideshare

Selenium• Works with most browsers and is

multi platform (c#, Java, Ruby)• Nuget packages

• Selenium.Support• Selenium.WebDriver

• WebDriver /IDE• Grid capabilities• Hub and clients• Simple jar file install commands

Page 9: Running agile testable content deployments from start to finish slideshare

Actual Tests

• NUnit• NuGet• Basic NUnit test

• What next?

Page 10: Running agile testable content deployments from start to finish slideshare

Nunit test

Example c# nunit test

using System;using NUnit.Framework;using RedGate.Deploy.WebAppTests.Pages; namespace RedGate.Deploy.SmokeTests{ [TestFixture] public class VersionTest : SmokeTestBase { [Test] public void LoginPageShowsCurrentVersion() { Version expectedVersion = GetType().Assembly.GetName().Version;  LoginPage loginPage = LoginPage.Load(Driver, SmokeTestUrlBase);  Assert.AreEqual("v" + expectedVersion, loginPage.VersionNumber.Trim()); }

Page 11: Running agile testable content deployments from start to finish slideshare

Summary

• Improve confidence in your deployment

• Adding tests is easier than you might think

• Automate gradually

Page 12: Running agile testable content deployments from start to finish slideshare

</talk>Code: https://github.com/EmmaArmstrong/SeleniumTesting

Emma Armstrong

@EmmaATester