We can’t live without connections and neither our tools can.

Enterprise Tester (ET) allows you to connect to other tools, like Defects and Requirements tools. We need to connect to Enterprise Architect (EA), our requirements tool.
It was a nice surprise to see how simple it is to connect to EA. The connection is done by importing directly from EA’s database without any other components between. Clear and simple. There are other ways but this one is the simplest.
It’s quick and it works well.

A Requirement in EA becomes a Requirement in ET.
A Use Case in EA becomes some Script Tests in ET, a Script for each Scenario.

In EA we organize requirements in a tree of packages. We import requirements to EA by package.
The complete tree is created, under the ET’s requirements package we specify. This way we can keep the same structure we have in EA and this makes easier to read. Depending on the complexity of model in ET we can import the complete model or just one package.

When requirements are modified or new requirements are created in EA we just have to import again the packages to update and add news.

Of course we can create requirements in ET manually. But, as I said, connections are our life!

(previous step Security)


When you install Enterprise Tester you’re asked to…

When you install Enterprise Tester you’re asked to create an administrator account. This is the first step into security.
The security system isn’t complex and gets simple to implement.
You have Groups of users and Users. Permissions are define by Group.
Users are independent from projects. instead you assign a User to projects – like in real life.
You can define permissions to all tasks in your team. To people who writes test scripts, the ones that manage iterations, the ones that execute and, very important, the ones that read your test scripts.
Although some of you think that writing test scripts is a waste of time and that you get more results if you spent that time testing, I think test scripts can be useful.
Like everything else in life, there must be a balance between what you write and what you get in return. When I write test scripts, I don’t get in too many details, I don’t describe every little steps. I try to describe what to do and spent more time describing what to check (I wrote check, not test !) to get it useful to others.
I think our test scripts are part of the product documentation. This is why, in Enterprise Tester, we have to create a Group of Users that will not write nor execute tests but will read tests.

Setting up Enterprise Tester after a break here…

Setting up Enterprise Tester, after a break here I am again.

Enterprise Tester is very easy to install. Once installed you configure it and work with it using web access.

The first step is to create your Organization, and Administrator account and set up your licence. You are ready to go.

An Organization can be your company, your department or your team. You may create more than one.
Our decision is to have one Organization that is our company.

For each organization you add your Enterprise Architect connection and configure your pick lists. Also available are Custom Fields. This is something I like very much, to personalize lists and add new fields.

Custom fields have a reasonable range of types and something better than that – a scope. This means you can have different customization in each of your projects or apply the same to the whole Organization. This can be very useful when you work with distinct projects, like web applications, smart phones apps, etc.

Next step: take care of security.

(previous step Reading about Enterprise Tester)

Reading about Enterprise Tester our new Test Management…

Reading about Enterprise Tester, our new Test Management tool. Next days will be great, learning and planning how to put it to work for us.
Since we are working with Enterprise Architect (EA) as a requirements tool, we plan to import requirements from there into Enterprise Tester (ET).

First we need to install it. This is the part I don’t like. It’s incredible how a setup can have so many questions and so many options! If we don’t take the right option we might have to start all over again.

Now things are getting better.
What do I know? I know that we will import requirements from EA and that we won’t use Defects management, because we have another tool to do this. This is a good starting point.