Hello and welcome to my second blog post “All About ET”, I really hope these posts will be useful in a practical way for new and existing users.  If there are things about Enterprise Tester that you want to hear about or if you have a better way of doing things then let me know!  Any feedback is always good.

At some stage in the not too distant future…  we will be implementing inbuilt project templates to allow Enterprise Tester users the ability to select which type of project they would like to establish, such as Agile, Waterfall or even Customized templates.  In the meantime, until we deliver that functionality you can still create the project structure you need (you can also make your own template by baselining… but that is another blog post for another day).

Waterfall Projects

When you add a project in Enterprise Tester the current project structure looks like this…

This structure is more suited to Waterfall projects where you might have a functional area covered in your script library  (your test scripts themselves would sit under each functional area and regression suite package accordingly).  Something like this:

If you are doing cycle based test execution your test execution folders could be structured like the screenshot below.   Using the fast drag & drop functionality from the script library the cycles can be created really quickly.

Agile Projects

You can easily change the folder structure by renaming your top level folders to support Agile projects.  As an example an Agile project may look like this:

As the sprints progress you could create sprint packages and a regression suite in the script library (your test scripts themselves would sit under each sprint and regression suite package accordingly).  So your script library might look something like this:

As test execution happens for each sprint you would drag and drop the packages (containing tests) from your script library into your sprint execution folder.

After three sprints your test execution structure could look something like this:

The project structure in Enterprise Tester is flexible so really it supports any type of project in which ever way you want to cut it.   Dragging & dropping tests from your script library means tests are easily transferable between sprints (lets face it, how often do we really get to “done” in a sprint?).

Anyway, I know there are many other structures people use for both Waterfall and Agile projects, we would love to hear how you see your projects structured in Enterprise Tester, so… let us know!

Tip! A regression test suite can be easily created by using the bulk copy functionality in Enterprise Tester after each sprint is completed.