Your SlideShare is downloading. ×
Running agile testable content deployments from start to finish slideshare
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Running agile testable content deployments from start to finish slideshare

421
views

Published on

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 …

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.

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
421
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • AboutUmbracoEmmaArmstrngTest EngineerRed Gate
  • 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.
  • Opportunity cost
  • 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.
  • java -jar selenium-server-standalone-2.14.0.jar -role hub java -jar selenium-server-standalone-2.14.0.jar -role node  -hub http://localhost:4444/grid/registerbrowser  browserName=firefox, version=3.6,platform=LINUXDesiredCapabilities capability = DesiredCapabilities.firefox();ebDriver driver = new RemoteWebDriver(new URL("http://localhost:4444/wd/hub"), capability);
  • Transcript

    • 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

    ×