Solution Expert Sessions

Unequivocally, Xpediter/Eclipse is one of the most convincing reasons for mainframe developers to voluntarily leave their comfort zone of TSO/ISPF and start using graphical user interafces for their mainframe debugging. 

As we know initially we can be frustrated until we are more experienced: "How does this library concatenation work?", "Where does this library version come from?", "How do I debug my IMS transaction?"

These questions and more are going to be answered during our webinar.

Topaz for Total Test has great potential to help mainframe development teams to start testing sooner in the development life cycle (i.e. "shift left") and make testing easier and quicker for developers than defining and running tests manually or by writing an maintaining their own test drivers and framework.

But - as with any tool - you need to know where, when and for which purpose to use it best. Our everyday experience tells us that using the right tool for the wrong purpose will lead to frustration - in the best case. Why should this be any different for a testing tool?

So, how can you determine if Topaz for Total Test is the right tool to use for your purpose? This webinar will highlight the considerations a developer should go through, before they even start thinking about using Topaz for Total Test - not to mention how to use it.

Topaz for Total Test uses Eclipse Projects and certain folder structures to store its test scenarios and assets. If not careful, very soon one gets overcrowded by the number of projects, folders, subfolder, scenarios ... until you have yourself in a tangle. Questions like: "Where is this scenario I recorded last week?", "I need to modify my program. Which scenarios do I need to consider?", "How can I create a new scenario from an old one?" are typical questions, we hear very often.

To prevent you from getting lost, before you even get going, we will answer these question and will explain the general folder structure within one "project". We will share experiences in what has worked when it comes to structuring your test case repository/ies. And once you have laid the foundation, how you can "grow" your repository, when it comes to extending test cases.

Finally. You have determined that Topaz for Total Test is the right tool for your situation. Your program has been prepared and you are ready to go.

But where do you start actually? How do you create your first test scenario? How can you make sure your scenario is testing what it is supposed to test? And how can you extend your test scenario to test more parts of your program? These are the main questions we will answer during this webinar.

In a previous webinar we have taken a look at the typical, standard use case for Topaz for Total Test - Virtualized Testing - from recording all the way to extending and re-baselining your scenario. But, admittedly, there are a few things to consider. 

In this webinar we will highlight all aspects of *recording* test scenarios.

• What are the different options for recording?
• What are the consequences?
• And what are the resulting use cases for the different options?

In a previous webinar we have taken a look at the typical, standard use case for Topaz for Total Test - Virtualized Testing - from recording all the way to extending and re-baselining your scenario. But, admittedly, there are a few things to consider. 

In this webinar we will highlight all aspects of *playing back* test scenarios. Especially:

• Where does Topaz for Total Test take configuration settings from? 
• What are the different options for storing these settings? 
• And what are consequences of the different options?