Test Driven Development - practical workshop

Is your software development process being crushed by too many bugs?

Hello,

Do your software development projects suffer from one or more of the following problems?

Software being delivered to the test environment and the testers immediately finding many bugs.
Bugs being fixed, but unknowingly one or more new bugs are introduced.
Code that is difficult to read and understand.
Developers quoting several days to make a change that you feel should only take a day.
New team member taking weeks to get up to speed on the code.
Developers fearing to make changes to code because there are no automated tests.
Code that is difficult to change because it is fragile.

If you answered yes to any of the above then you should consider implementing Test Driven Development (TDD) on you existing and new projects.

Here are some of the benefits of using TDD

Would you like to eliminate all those panic meetings where you have to try and explain why the number of bugs is increasing, rather than being close to zero?

Would you like to produce software that the testers enjoy testing and customers are eager to use?

Would you like the business stakeholders and customers to have faith in your ability to deliver useable applications?

There is a software design technique that goes a long way to achieving the above goals.

Far less bugs
With this technique you will have significantly less bugs being reported by the test team.

Any bugs that are reported will be easier to find and fix. You'll also eliminate 'bug bounce' where the fix of one bug causes the testers to discover another new bug.

Easier to maintain code and higher quality code.
You've probably experienced or heard a Developer saying something like "I just can't understand this code, it does not make sense, it could be weeks before I can implement the change request that you want."

Now you can have code that is easy to understand, easier to maintain and easier to modify and enhanced. Like all good design techniques, the technique that I want to show you leads to clean uncluttered code.

Used by Credit Suisse, BBC, Accenture, Swinton Insurance, MessageLabs and other leading companies.
This technique is used by many leading companies, the list is constantly growing. Make sure that your rivals do not leave you behind. Whilst you are fixing bugs on a project that has been running for 3 years, your rivals are on to their next project responding to a profitable opportunity in your market.

More controlled and calmer release period.
With near bug free code, you will be far more in control. You'll be able to stick to your release schedule.

You'll be able to avoid the panic and stress filled emergency releases that you try and do, which always seem to end up causing more bugs and more problems.

A happy test team.
Yes I know it sounds unbelievable, but you can actually have a happy test team. A team that can get on with testing the deep and complex business functionality without being hampered by what seems like a million problems that should never have made it into the test environment.

Eliminate evening and weekend working.
When you find that your team have to work evenings and weekends then it is an indication of failure. Using correct design techniques can dramatically reduce your bug count and thus eliminated the need for overtime working. This helps to keep the project within budget.

Feel positive about the progress of your application.
Do you hate going into the weekly meetings to report on the progress of your project? Wishing that you were somewhere else when you have to say "Well, last week there were 127 bugs, we have fixed 5, but unfortunately the testers have found another 12".

How about if you could go into your progress meeting and say "We have fixed the 5 bugs from last week, and the testers have not been able to find any further problems over the past three days." That would make you feel good, make you feel like you are satisfied with your job.

Stop having panic crisis meetings where you try and categorise and prioritise hundreds of bugs. With just a few bugs the Developers will have fixed them all before you can decide who should be at a prioritisation and categorisation meeting.

Here's what people are saying on Twitter about TDD.

Huge payback today as I made big changes to a library and my tests saved me from surprise after surprise.

TDD is so incredibly nice! I just did a major refactoring of my pet project and I know for certain that I didn't break anything.

I really don't know how you do anything like a decent web application without TDD and a good CI framework these days.

Maybe those who think TDD is slower just have someone else cleaning up their bugs.

Up to date technical design documentation.
How would you like to have technical design documents that are always fully up to date? Document that Developers are happy to create? Documents that are easy for new Developers to understand?

With this technique you get far better design documents than those printed documents that are put on a shelf, get rapidly out of date and Developers are not interested in reading.

Easier for new Developers to learn the code.
With this design technique it is far easier for new Developers or Developers from other teams to very quickly get up to speed and be productive and contribute to the coding.

Down to Earth
This course is presented in a down to earth manner. It's as if I am sitting with a Developer at their desk and taking them step by step though the design technique that leads to significantly less bugs. The video shows me actually designing a real application and demonstrating in a very practical manner how the design technique is implemented.

The course
The course has been written by Senior Software Developer who has been involved in developing many types of business applications during the past sixteen years.

Compare TDD with traditional development
As an example, the Developer was in a company where two similar sized applications were being developed. With budgets of several million pounds. One project used TDD, the other did not.

The non TDD project constantly had many bugs waiting to be fixed, towards the end of that project the bugs were getting unmanageable, with around three hundred bugs in the bug report system. There were a lot of unhappy people around. Bugs were being fixed and these fixes uncovered other bugs, it was a losing battle.

The project using TDD was delivered on time. Throughout the test phases there were never more than twenty bugs outstanding. And most of these were misunderstandings of the specification rather than any technical bugs. Bugs were easy to fix and did not result in other bugs being introduced.

What is Test Driven Development
Test Driven Development (TDD) is a technique where Developers design the code by writing a test first. By having a test, the Developer is expressing an understanding of what is required of the code that is about to be written. The code is then designed, and the test is then run to prove that code.

Gradually the application will have hundreds and possibly thousands of tests to support it. These tests can all be run to ensure that everything is still working correctly. New code is never written until a test has been created.

These tests serve as the technical design document. They are constantly up to date. The tests allow Developers to easily see what a piece of business logic should be doing.

Hundred of hours of experience
This course condenses several years of knowledge into a five hour viedo that will enable you to quickly learn and implement TDD. This course is intended for complete beginners and will bring you up to intermediate level.

Very quick return on your investment
The cost of having bugs in your application is incredible. If one single bug makes it to the test environment the cost could be several hundred pounds. Lost testing time, code fixing, re-releasing, missed deadlines more meetings, internal politics and loss of faith.

If you have upwards of one hundred bugs the cost both financially and professionally are astronomical. If you were to send 5 Developers on a one day instructor based course, the cost could be in the region of £4000.

Plus the course may be at a pace where the Developers do not learn everything. Or a Developer may need to review a point but the instructor carries on due to time constraints.

And there is always a chance that one of the Developers is having an ‘off' day and does not benefit from the instructor based course.

In this self paced video training course, you'll watch me create a small application using TDD.

With a self paced course you have the chance to review points, to re-wind, to take breaks, to share the course with your team members The cost of this course is just £247. This is a huge saving compared to instructor based training courses. The cost is probably less than the costs associated with one or two bugs.

Money back guarantee for 30 days. If you don't like the workshop for whatever reason. Just send it back within 30 days of purchase and I will refund the workshop cost.

Bonus
Unlike most training courses, I will not leave you to cope on your own after you have completed the course. You get email support for three months. If there are any problems that you have in understanding the workshop or anything related to TDD just email me and I will provide you with an answer or point you in the right direction of further help.

Summary
By using TDD you can dramatically reduce the bugs being released to the test and production environments. This will save you £000s.

How to place your order
Pay with your Credit or Debit card via PayPal (You don't need a PayPal account). Alternately you can send a cheque to the address shown on our contacts page. The course will be dispatched within three working days of your payment being cleared. Click the Buy Now button and have your card details ready.

Just £247. Compare that to an Instructor based course!

Plus £3 Postage and Packaging

Only suitable for Microsoft Windows

Remember, you do not need a PayPal account.

P.S.
Remember, using TDD will greatly reduce the number of bugs that you have in your software application.

Don't forget that you have the satisfaction of a 30 day money back guarantee.

And unlike must course providers you get a bonus of email support for 3 months.

Order your copy now for just £247.

We look forward to helping you implement TDD on your current and future applications.