Automated test/release cycle – Is it for me?

Testing 1, 2, 3

The 10th of March, we will be talking about automated tests/release cycles for EPiServer (and general .NET-projects). what does it really mean? You might be thinking: it’s not for us, or even better, we already have it.

Regardless if you are a customer or consultant company, you have a lot to benefit from the techniques we will be talking about.  As customer/developer, you might have come across many different ways of releasing new or upgrade existing EPiServer sites.

In order to meet todays fast changing requirements web sites needs testing (web 2.0 needs testing)

In order for you to find out if you if you can benefit from the topic we will be talking about, please answer the following simple questions:

1. How do you go about when relasing/upgrading EPiServer site(s)?

1. We have a guy who takes care of that
2. Someone manually copies the code that has changed to the test/production server
3. I dont even understand the question, but whatever we are doing it seems to be working alright
4. We release new functionality by using nightly builds produced by our build server

2. How do you test your EPiServer site?

1. Test? I trust the developers when they say that it’s working
2. All testing is handled by an external company
3. We unit test some functionality and use manual tests for the GUI
4. We have an fully automated test cycle for both functionality and GUI

4. Whats your overall coverage?

1. Que?
2. Thats rude, are you referring to my Comviq-frilla?
3. Somewhere around 10-50%
4. Over 50%

If you answered “4” on all questions, congratulations you  probably know most of the things we will be talking about, but you could still drop by. Otherwise you will definitely benefit from coming to our session, Welcome!

/Emil & Micke