I tried re-installing, repairing the installation, I even deleted all fdata on appdata and user, yet the problem didn’t sub-side.

Only after searching multiple forums, and resources I found this post that solved the problem:
http://www.sempf.net/post/e2809cThe-Application-Cannot-Starte2809d-in-VS-2008-after-install-of-VS-2010.aspx

On the two machines I installed the STAF application from: http://staf.sourceforge.net/. Here you have to download according to your machine 64x, 84x, Windows, Linux, etc…

Once you do that you should have on both machines one folder with the following name: C:\STAF.

To do a first check if the installation went well go to your Start – Programs – STAF 3.4.2 and execute the Start STAF 3.4.2. At this moment you will see only a command line window with the name of you machine.

STAF/STAX Process

Other thing that should have in account are the java directory environment folder that should be set. On Computer – Properties – Advanced system settings – Environment Variables and on the path variable add C:\Program Files\Java\jdk1.6.0_20\bin (This is to 64x machines).

Next on the machine that will act as the controller (that is the machine that will command the other test controllers) you should edit the file c:\STAF\Bin\STAF.cfg. This file should be configured as follow:
# Turn on tracing of internal errors and deprecated options
trace enable tracepoints "error deprecated"

# Add default service loader
serviceloader library STAFDSLS
SERVICE STAX LIBRARY JSTAF EXECUTE {STAF/Config/STAFRoot}\services\stax\STAX.jar
SERVICE EVENT LIBRARY JSTAF EXECUTE \{STAF/Config/STAFRoot}\services\stax\STAFEvent.jar
SET MAXQUEUESIZE 10000

Next on the machine that will run the tests the same file should be configured as follow, the main point here is the section # Set default local trust where the name of the first computer should be set. This can be the nick name (which I suggest) or the IP of the machine:

# Add default service loader
serviceloader library STAFDSLS
SET MAXQUEUESIZE 10000

Once again on the machine that will act as the controller that is the machine that will command the other test controllers you need to install STAX, you can download from the same link http://staf.sourceforge.net/ this service should be installed on the default directory C:\STAF\Services, here you can create a folder named STAX and copy the filed to here.

You can know notice that this lines:

SERVICE STAX LIBRARY JSTAF EXECUTE {STAF/Config/STAFRoot}\services\stax\STAX.jar
SERVICE EVENT LIBRARY JSTAF EXECUTE \{STAF/Config/STAFRoot}\services\stax\STAFEvent.jar

point to that location.

At this point is important that you can open a command window and execute java.exe with no problem.

If all went all you can know create you first simple script to execute a simple command on the machine that will execute the automated tests, the only point that you should pay attention is to the name of the machine where the tests will run, here is ‘test08.primavera.local’:
StaxRunNotepadProcess (rename .doc to .xml)

This little script will only open the Notepad on the test machine.

If the installation are good then open a command line prompt and execute the followinf command java -jar Services\STAX\STAXMon.jar. This should open a little application. Here access to Submit new Job button select local machine and pointo to the location were you saved the script that run the notepad and execut once again the Submit New Job.

If you successfully installed the framework them you can execute in batch several tests on several machines with the following script, note that the language used is python: StaxBatchProcess (rename file from .doc to .xml)

I highlight the sessions “Unit Testing Silverlight and Windows Phone Applications” with Jeff Wilcox where he bring some news over the Unit Testing Silverlight framework, the other is “Improving Software Quality for the Modern Web” by Euan Garden.

The automation group needed a tool that can manage effectively the virtual machines, where they can setup a set of actions to be executed on a machine.

The first option I choose was the solution from VMWare, in this case the VmWare Server 2.0, that is completly free. Can be downloaded after registration on the site of the VmWare.

The other tools to work and manage Virtual Machines is the IX API from VmWare and that is also free, but as this API is very difficult to work I download also the application VmWareTasks that is a wrapper for the previous API.

So how can I implemente a virtual management so can be used for all? After the tools choice, I become to think what is the best way to tell a machine what actions must execute, and in what order.

The solution was to create a Xml file with all possible actions that a user can execute on a virtual machine.

After the structure is defined I only need to read the Xml file and execute the possible actions using the VmWareTasks API.

A sample project can be downloaded here. (Works with VS2010, after the download rename from .docx to .zip)

Two things that this project needs:

The second you need only to create a project console and in the Main method of the class Program.Cs write the following code:


///
/// Entry point to manage virtual machines.
///
class Program
{
static void Main(string[] args)
{

VirtualMachineManagementService virtualMachineManagement = new VirtualMachineManagementService();
virtualMachineManagement.Manage(virtualMachineXMLFile);
}
catch (Exception exception)
{
Console.WriteLine(exception.Message);
Console.ReadLine();
}
}
}


The explanation for this logo comes from the defintion of automation, the question mark on the head is that we must always question what we are doing and if there is a better way to do that, finally the spark is just a joak where the team will do several sparks before achieving the goals.

I hope you like it…

We can say that is not really the first blog to talk about software testing but it is the first to innovate in the sense that we want in one place together all information relating to the area of test automation software, not forgetting the area Software Quality Assurance where this fits.

In this blog we explain all concepts and procedures relating to the topic Software Quality Assurance or how it came about, what is its purpose, which the concepts and methodologies relating to it. Let’s try to be as succinct as possible, so that in one area are concentrated in the responses both to a tester beginner to expert.

As the name implies here want to concentrate all the experience gained, all the research done, and as well as means for automating software testing.

Thus we will have available a forum where all the testers where you can ask questions, share experiences, create discussions and have access to documentation about the areas in question.
We also have an area on the software used for the purpose of testing software is a Web platform, Windows, among others. As software for the automation of them.

This may be software on the Web or even created by the testers themselves if they want to make in order to simplify, improve and give more guarantees surrounding the whole procedure.

Let’s try that this blog is always written in two languages (Portuguese and English) so that its contents and exchange of experiences available is as inclusive as possible.

With best wishes and hope that this blog is a great reference point to help all the testers,

Eduardo Ribeiro (Co-Fundador)
Miguel Marques (Co-Fundador)

Podemos dizer que não é, realmente, o primeiro blog a falar sobre testes de software mas é o primeiro a inovar no sentido como queremos que num só local reúna todas as informações relativas à área de automatização de testes de software, não esquecendo a área de Software Quality Assurance onde esta se encaixa.

Neste blog vamos explicar todos os conceitos e procedimentos relativos ao tema Software Quality Assurance ou seja como surgiu, qual a sua finalidade, quais os conceitos e metodologias relativas ao mesmo. Vamos tentar ser o mais sucintos possíveis, de forma a que num só espaço estejam concentradas as respostas quer para um tester iniciante até ao mais experiente.

Como o próprio nome indica aqui pretendemos concentrar toda a experiencia obtida, toda a pesquisa realizada, bem como e disponibilização de meios para automatização de testes de software.

Deste modo vamos ter disponível um fórum onde todos os testers onde poderão colocar questões, trocar experiências, criar discussões e ter acesso a documentação disponível sobre as áreas em questão.

Vamos ter também uma área relativa a software utilizado para o efeito de testes de software seja plataforma Web, Windows, entre outras. Assim como software relativo à automatização dos mesmos.

Este, pode ser software existente na Web ou mesmo criado pelos próprios testers que o queiram disponibilizar de forma a simplificar, melhorar e dar mais garantias todo o procedimento envolvente.

Vamos tentar que o presente blog seja sempre escrito em duas línguas (Português e Inglês) de forma a que, o seu conteúdo e troca de experiencias existentes seja o mais abrangente possível.

Com os melhores cumprimentos e votos que este blog seja um grande ponto de referencia de ajuda para todos os testers,

Eduardo Ribeiro (Co-Fundador)

Miguel Marques (Co-Fundador)