running agile testable content deployments from start to finish slideshare

Running agile, testable content deployments from start to finish

Emma Armstrong

@EmmaATester

Continuous Delivery

The aim to rapidly and reliably release to production.

Frequent Releases

Deliver user value

First to market

Feedback

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?

Process

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

What is missing?

Demo

Testing

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

• What to use• NUnit• Selenium

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

Actual Tests

• NUnit• NuGet• Basic NUnit test

• What next?

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()); }

Summary

• Improve confidence in your deployment

• Adding tests is easier than you might think

• Automate gradually

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

Emma Armstrong

@EmmaATester