SW Test Automation Framework

Tracker: Feature Requests

5 A C/C++-implementation of STAX - ID: 1718526

Last Update: Comment added ( tommi_r )

Details:

STAF seems like an extraordinary test framework, and STAX a likewise
extraordinary execution engine for STAF. However, STAX's dependence on Java
means it cannot be used in very primitive environments, such as with
embedded Linux devices. For that reason, I propose that STAX or a similar
execution engine be created without a dependence on Java.

The featureset of this non-Java execution engine does not have to be
identical to STAX: it would be enough to have a basic, scripting-supportive
execution engine that is usable to run compiled binaries, retrieve return
values and facilitate basic result comparison. This would be enough to get
a foothold in environments where Java is out of the question.

I feel this would be a very significant improvement to STAF.

Submitted:

Tommi ( tommi_r ) - 2007-05-14 10:12

Priority:

Status:

Open

Resolution:

None

Assigned:

Nobody/Anonymous

Category:

Platform

Group:

Future

Visibility:

Public

Comments ( 2 )

Date: 2007-05-15 10:31 Sender: tommi_r The setup you propose is indeed feasible, also in our environment. However, I would still like to maintain that in certain situations it is better to execute test scripts locally. For example, when developing tests on a number of different target hardwares, it is cumbersome to always be configuring the environment before running or debugging the tests, as opposed to just running the test code on the target machine. So from a test development point of view, some kind of script execution support on the target hardware level would be interesting.
Date: 2007-05-14 13:47 Sender: crankin_work Thanks for the compliments. I'm glad you like STAF/STAX. Note, STAX is most commonly run on a central system where the jobs execute processes remotely. This allows the target system(s) to only run the basic STAF daemon while the "heavyweight" stuff runs on a central system. Would this type of setup work in your situation, or do you actually need STAX (or something similar) to actually run on the target system?

Date: 2007-05-15 10:31
Sender: tommi_r

The setup you propose is indeed feasible, also in our environment.
However, I would still like to maintain that in certain situations it is
better to execute test scripts locally. For example, when developing tests
on a number of different target hardwares, it is cumbersome to always be
configuring the environment before running or debugging the tests, as
opposed to just running the test code on the target machine. So from a test
development point of view, some kind of script execution support on the
target hardware level would be interesting.

Date: 2007-05-14 13:47
Sender: crankin_work

Thanks for the compliments. I'm glad you like STAF/STAX. Note, STAX is
most commonly run on a central system where the jobs execute processes
remotely. This allows the target system(s) to only run the basic STAF
daemon while the "heavyweight" stuff runs on a central system. Would this
type of setup work in your situation, or do you actually need STAX (or
something similar) to actually run on the target system?

SW Test Automation Framework

Tracker: Feature Requests

Comments ( 2 )

Attached File

No Files Currently Attached

Change

No changes have been made to this artifact.

About SourceForge

Find Software

Develop Software

Community

Help