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.

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

2. Continuous Delivery
The aim to rapidly and reliably release to
production.

3. Frequent Releases
Deliver user value
First to market
Feedback

4. 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?

5. Process
1. Write your content
2. Add your content to CMS
3. Deploy your content
What is missing?

6. Demo

7. Testing
• What to test
• Are all the pages there?
• Is it the correct version of the page?
• What to use
• NUnit
• Selenium

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

9. Actual Tests
• NUnit
• NuGet
• Basic NUnit test
• What next?

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

11. Summary
• Improve confidence in your deployment
• Adding tests is easier than you might
think
• Automate gradually

12. </talk>
Code:
https://github.com/EmmaArmstrong/SeleniumTesting
Emma Armstrong
@EmmaATester