Test
Run-Time Controller (TRC)
Help
Quick navigation within this help – click on the links below:
How
do I open TRC GUI?
How do I close TRC
GUI?
How
do I get general help about TRC?
How
do I log in to TRC?
How do I log
out from TRC?
How do I hand off
to someone else?
How
do I load a new test request?
How
do I close a test request?
How
do I expand and collapse an activity group?
How
do I select which activities to execute?
How
do I start executing a test request?
How
do I suspend the test request after the current activity?
How
do I put the current activity on hold immediately?
How
do I terminate the test request after the current activity?
How
do I abort the test request immediately?
How
do I see the attachments to the test request?
How
do I use the Electronic Note Book?
Introduction
Test Run-Time Controller (TRC) is the operator's interface to execute test requests within CyFlex. It allows the operator to control the execution of test requests that were previously created by the test engineers. Test Engineers use Test Request Interface (TRI) to create test requests.
While it is not necessary to understand all that is going on behind the scene, it might help to know that there are two parts to TRC, one part that works behind the scenes and does all the work, as well this part, the TRC GUI, which instructs the other part what to do. Due to this division of labor, the TRC GUI itself can be closed without impacting the test execution function of TRC.
If you want to get more information:
Click
here to get general information about the test request system.
Click
here to get description of the terminology used in the test request
system.
Click here to get
information about the various sections of TRC window.
Simplified sequence to execute a new test request
Log
in to TRC GUI.
Load the new
test request.
Start
the test request
Wait for all activities to be done.
Close
the test request.
Log out from
TRC.
These and other steps are described in detail below.
The TRC GUI is automatically started when CyFlex starts and it should normally be left open. If you cannot see it on the desktop, it might be minimized. Search in the panel at the bottom of the monitor and if it is present there, click on the icon to return it to the desktop. If the TRC GUI is indeed not open, in any terminal, type the command:
start_trc
Normally you should not close the TRC GUI. If you do need to close the TRC GUI, click on the “X” button at the top right corner of the TRC window. Note that closing TRC does not affect (e.g. stop) the test request that might be in progress.
How do I get general help about TRC?
Click on the “Help” button at the right end of the top row of buttons. You are looking at the help pages right now.
When the TRC GUI is first opened, it is not logged in. You will be able watch the current state of TRC. However to be able to control the functions of TRC, you must first log in.
Click on the “Login” button at the top left
corner.
A window will open. Enter your username and password.
(Until the security system is fully implemented, you might be able
skip this step.)
Click the “OK” button. (If you don't want to
login, click the “Cancel” button.)
Your name should appear in
the User field to the right of the buttons. Your name is shown so
that someone who comes to the test cell while you are away will know
who is responsible for the test.
When you are no longer responsible for managing the test, you should log out from TRC.
Click
on the “Logout” button in the top button row.
The action is
immediate. If you didn't mean to log out, just log back in – no
harm done.
How do I hand off to someone else?
When someone else takes over responsibility for the testing, you should hand off TRC to that person.
Click
on the “Handoff” button in the top button row.
A window will
open up prompting the new person to log in, same as for a normal
login as described above.
You are automatically logged off.
There
is no difference from your logging off and the new person logging in.
This is just a short cut.
How do I load a new test request?
Only one test
request can be active at a time in the CyFlex test system.
Verify
that test request state (“TR State” field in bottom right corner
of the buttons area) indicates “NO_TR_LOADED”.
If it is
TR_LOADED, you must first close that test request.
If it is
TR_RUNNING, you must first terminate / abort that test request and
then close it.
Click
on the “Load TR” button in the top button row.
A window will
open. Enter the test request name or partial match . Click “Next”.
(For partial match, use ? to match a single character, * to match
zero to any number of characters.)
A new window will open with the
list of test request names that match. Select the test request to
load and click “Next”. If the search did not show the test
request of interest, click “Back” and search again.
A new
window will open with list of revisions available for that test
request, together with the date and time when each revision was made.
The revision has the format of X.Y where X is the major revision and
Y is the sub-revision. Select the revision of interest and click
“Finish”. The revision of interest is often the latest one, but
it may not always be so.
The test request table section should
fill in with the activities from the test request.
If the test
request had been executed previously at this location or a different
one, the test request will start with the saved state from that
execution.
The test request name, revision number and the
sub-revision number should appear in the section to the right of the
buttons.
How do I close a test request?
When you are
are done executing and/or no longer needing a test request, you
should close it. When you close a test request, the state of that
test request is saved in the test request system. This feature allows
the test request to be reloaded in this or another test facility at a
later time at exactly the same point in the execution
sequence.
Verify that the test request state (“TR State” field
in the bottom right corner of the buttons area) indicates
“TR_LOADED”.
If it is “TR_RUNNING”, the test request must
be terminated / aborted first before it can be closed.
Click
on the “Close TR” button.
This action is immediate. If you
didn't mean to close it, just open it back again – no harm done.
How do I expand and collapse an activity group?
The test request system allows a group of activities to be collected together in what is known as an activity group. This is strictly for convenience of representing long and complex test requests into comprehensible chunks. The activities within an activity group may be shown in expanded or collapsed format. You know that an entry in the activity list is a collapsed activity group by the “+” sign next to the activity number.
To
expand a collapsed format, click on the “+” sign on the activity
group line.
To collapse an expanded format, click on the “-”
sign on the activity group line.
How do I select which activities to execute?
By default when a test request is loaded for the first time, all the activities are enabled to be executed. This is indicated by the check mark on each of the entries in the “Enabled” field in the activity list table.
To
select an activity to be executed in its turn, the check mark should
be on.
To prevent an activity from executing in its turn, the
check mark should be off.
How do I start executing a test request?
By default when a test request is loaded for the first time, the starting point in the test request is the first activity. This is indicated by the radio button in the “Start At” field of the activities table.
To
move the starting point to any other activity, move the radio button
to that activity line.
Click on the “Start” button below the
“Login” button.
A window will open ask, asking you to confirm
your starting point, as well as optional sub-activity starting and
ending. (Sub-activities have to do with certain long tests such as
steady state mapping driven by test tables.)
Adjust if necessary
and click on the “OK” button.
As soon as the test request
starts, the “Start button will be grayed out.
How do I suspend the test request after the current activity?
This feature is used can be used to temporarily suspend automated testing after the current activity is finished in order to do some manual work and the automated testing is resumed. This is different from “Hold” which puts the activity on hold immediately.
Click
on the “Suspend – After Current Activity” button.
The test
request state (“TR State” field to the right of the buttons)
should change to “WAITING”.
When the test request state
changes to “TR_SUSPENDED”, the test request is in suspended state
and the “Start” button changes to read “Resume”.
After
completing whatever was intended in the suspended state, click on the
“Resume” button to continue with the test request.
How do I put the current activity on hold immediately?
This feature must be used with CAUTION and knowledge of the activity that is in progress. Due to the multiple layers under which CyFlex tests are done, not all activities can be put on hold correctly and/or safely. Check with the support people to know which activities can be used with this feature.
While
an activity is in progress, click on the “Hold – Immediately”
button.
The test request state (“TR_State” field to the right
of the buttons) will change to “TR_HELD” and the “Start”
button will change to the wording “Release”.
When the cause
for the hold is over, click on the “Release” button.
How do I terminate the test request after the current activity?
The feature is used to terminate the test request when the current activity is completed. This is different from “Abort” which stops the activity and test request immediately.
Click
on the “Terminate – After Current Activity” button.
The test
request state (“TR State” field to the right of the buttons)
should change first to “WAITING”
When the activity is
completed, the state will change to “TR_LOADED”.
A terminated
test request may be restarted at any appropriate activity.
How do I abort the test request immediately?
Aborting the test request stops the current activity immediately and prevents execution of the subsequent activities.
Click
on the “Abort – Immediately” button.
Processing of the
current activity and the test request are immediately terminated. Due
to the multiple layers under which CyFlex tests are done, not all
activities may respond completely to the abort request. Additional
manual actions might be needed under those conditions.
The test
request state (“TR_State” field to the right of the buttons) will
change to “TR_LOADED”.
An aborted test rquest may be restarted
at any appropriate activity.
How do I see the attachments to the test request?
The test request system allows miscellaneous files to be attached to the test request. These may be files that are automatically used in certain portions of the test (e.g. ecfg files used by the ECM communication program). They may also be files that are automatically displayed through “Operator Action” activity or any file that the test engineer needs to convey to the operator. These files can be viewed and/or copied at any time the test request is loaded.
Click
on the “Attachments” button.
A directory display of the
directory where all the attachments are stored will open.
Any
appropriate action such as opening a file using existing applications
on the CyFlex computer or copying the file to another location may be
done.
How do I use the Electronic Note Book?
There is a convenience button on the TRC GUI to access the E-Log applications.
Click
on the “E Log” button located on the bottom right of the
buttons.
This will open up the e-log viewer and editor window.