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.
Have you ever driven somewhere and not known how you got there? That is the aim for continuous delivery. However there are things we need to do to enable that to happen. What is the aim for continuous delivery?
Not only are bug fixes sitting on the shelf, but the developers’ mental model of the software is in the future, so they struggle to help support engineers. Both of these factors coupled together leads to a bad support experience.
How do you know what you added works.How do you know what you deployed works?
What is the minimum testing you can do to ensure the right information is being displayed.
• What to test
• Are all the pages there?
• Is it the correct version of the page?
• What to use
• Works with most browsers and is multi
platform (c#, Java, Ruby)
• Nuget packages
• WebDriver /IDE
• Grid capabilities
• Hub and clients
• Simple jar file install commands
• Basic NUnit test
• What next?
Example c# nunit test
public class VersionTest : SmokeTestBase
public void LoginPageShowsCurrentVersion()
Version expectedVersion = GetType().Assembly.GetName().Version;
LoginPage loginPage = LoginPage.Load(Driver, SmokeTestUrlBase);
Assert.AreEqual("v" + expectedVersion, loginPage.VersionNumber.Trim());
• Improve confidence in your deployment
• Adding tests is easier than you might
• Automate gradually