1 1521-Fap1302050eng

Ericsson Internal
TEST INSTRUCTIONS 1 (23)

Prepared (also subject responsible if other) No.
EAB/FPR/CN ERAKNML Mikael MK Karlsson 1/1521-FAP 130 2050 Uen

Approved Checked Date Rev Reference
EAB/FPR/CN Per E Larsson 2013-02-01 G
CSM2.0 automated node test in CTS environment
History
Version Date Adjustments

PA1 2011-04-12 First draft
PA2 2011-04-14 Added some post test activities
A 2011-06-08 First release
B 2011-07-14 Update info collection dialog. Added quick cabling
instruction appendix.
C 2011-08-28 Created separate chapter for test plan execution
and the generic message box. Some clarifications
in the various chapters.
D 2011-10-25 General update and virtual cabling instruction.
E 2012-02-24 Updated for bartrack support
F 2012-03-30 Parallelism InitTest, Show 1521 in Idefix
G 2013-02-01 New testmethod added, Retestcheck
Contents
1 CTS .......................................................................................................... 2
1.1 Hardware requirements .............................................................. 2
1.2 Software requirements ............................................................... 2
2 CSM 2.0 node and magazine overview ................................................ 3
3 Automated Node Test ............................................................................ 3
3.1 Control 48V CTS power and configuration of CTS Neptune ...... 4
3.2 The generic message box .......................................................... 4
3.3 How to start the test ................................................................... 5
4 Running the test plan ............................................................................ 8
4.1 InitTestEnvironment ................................................................... 8
4.2 The virtual cabling instruction ................................................... 12
4.3 Start.PowerSupplyControl_ON ................................................ 13
4.4 SiteController.Test ................................................................... 14
4.5 ReadMagazineData ................................................................. 15
4.6 MagX.Test ................................................................................ 17
4.7 BarTrackNode .......................................................................... 20
4.8 HWInventoryToQSP ................................................................. 20
4.9 End.PowerSupplyControl_OFF ................................................ 20
4.10 GenerateTestReport ................................................................ 20
Ericsson Internal

4.11 CleanUp ................................................................................... 21

4.12 SaveBlobs ................................................................................ 21
4.13 Todo after the test .................................................................... 21
5 References ............................................................................................ 21
6 APPENDIX ............................................................................................. 22
6.1 Login to devices ....................................................................... 22
6.2 Sign off and Distribution of the test report ................................ 22
6.3 Paths relevant for the test ........................................................ 22
6.4 CSM 2.0 support and knowledge ............................................. 22
6.5 Quick cabling instruction .......................................................... 22
Abstract
This document describes how to execute an automated node test for the Core
Site Multiplexer 2.0 (CSM2.0) in the Common Test Solution (CTS)
environment.
Application
Test instruction is valid for NPC Katrineholm only or other sites adopting the
CTS test environment.
1 CTS
1.1 Hardware requirements
This test program requires a CTS Neptune hardware of revision R1D or

higher.
A printer connected to the CTS Neptune or connected to the ECN which is

present in the CTS running Windows Vista OS.
The test object should be connected to the CTS Neptune according to cabling
instruction [3].
1.2 Software requirements
The test program requires the CTS API R1C or higher to be installed on the
CTS Neptune.
Necessary test program files are automatically fetched when Idefix starts. It is
required that the CTS Neptune is prepared with the CSM function modules
before test starts which can be found in reference [4].
In the production environment, all CTS Neptune are already prepared with
correct software and are ready to be used.
Ericsson Internal

2 CSM 2.0 node and magazine overview

• A node always contains a cabinet. If an ESC is present, it is a ‘Node
Subrack’ otherwise it is defined as an ‘Expansion Subrack’
• An empty magazine contains 2 CPFU boards and 2 CMB boards. This

configuration is not sent through node test flow as for today. Though,
this test program can handle this case and will only perform tests
relevant for that equipped hardware (i.e. excluding traffic tests).
• An equipped magazine always contains 1-4 TLI boards. The

configuration is called ‘Expansion Magazine’ and is a valid
configuration for this test program.
• TLI boards can be of two types, balanced or unbalanced. There is no

difference in node test, hence the definition simple TLI. A node or
magazine may not contain mix of TLI board type.
• Board and port numbering as shown below:
Figure 1. A CSM2.0 magazine with port and board definitions.
3 Automated Node Test

The automated test for CSM2.0 consists of one Idefix program which is
supposed to be fully executed in order to state the node test as performed
which is the way it is done in test mode ‘auto’. In cases of fault finding and
other special cases the ‘manual’ test mode can be used.
Always start the test program in mode auto in all normal cases. If not, the ‘test
status’ flag will not be set to ‘PASSED’ in Bartrack and must be set manually
before status ‘SHIPPED’ can be set.
Ericsson Internal

3.1 Control 48V CTS power and configuration of CTS Neptune
When testing in a CTS Neptune environment, all power control will be done
automatically. The operator is free to choose the manual mode to control
power but default is always to use the automatic power control. The power
selection is done in a dialog after the test has been launched. This feature
can be useful when faultfinding etc or when running the test program from a
regular PC client, if so the rest of the setup is skipped and the operator is to
configure the test environment manually. Manual configuration is not covered
in this document.
The automatic configuration of the CTS Neptune is:
• Setup of the network interface for ‘Node Network’-interface.

- The network interface towards the test object is reset and set to
10.10.64.100/16.
• Setup of the CTS Neptune Switch.

- The switch is reset to clear previous settings and is then used with
default settings as a normal switch.
• Killing any virtual machines running in VMWare. Since other test

programs make use of virtual machines to access the CTS server and
similar features, VMWare is reset to be sure no interference can occur
from a VM.
• Flush of ARP table before each node and each magazine.

- To avoid weird behavior when switching test objects fast or moving
cables between magazines during test, the ARP table is flushed since
CMB boards/ ESC always will have the same IP address.
The configuration is automatically done in the Idefix program as test points.
3.2 The generic message box
Throughout the test, there will be a message box informing the operator to
perform actions, warnings, information and questions. The text in the box is
self explanatory. Depending on what situation, buttons, text and image will
change. Example is illustrated below:
Ericsson Internal

Figure 2. Example of the generic message box used to inform operator.
3.3 How to start the test
To start the test program, double click on the Idefix icon on the desktop. A
window will appear prompting for the serial number of the test object (DUT).
Figure 3. The dialog when starting a new test.

Ericsson Internal

‘Test type’ is always CSM20. Make sure the correct test program is selected
before serial number scan is performed. The serial number to use is located
on the label located on the cabinet or the label placed on an expansion
magazine.
- If cabinet exists, scan/use serial in the cabinet frame. The

product number is the same as can be found on the order
trigger.
- If test object is an expansion magazine, the label to use is

placed BESIDE the ‘empty magazine’ label. The product
number is the same as can be found on the order trigger.
Figure 4. Location of the main product label on an expansion magazine.
A validation will be done towards the leading 3 letters in the serial number and
matched towards a list of valid factory serial signatures.
Example: A Katrineholm site serial is A061234567, if the ‘empty magazine’

label is scanned instead (X111234567) the test program will inform the
operator about the mismatch since A06 != X11.
Ericsson Internal

NOTE: If the serial number is entered using a scanner, the test will start
immediately after a serial has been read since the last letter in the label is
followed by a ‘carriage return’ character. Make sure the proper run mode and
correct product has been selected before scan of label is performed.
The test plan consists of both groups and points, groups are represented as a
yellow sack and points are shaped as magnifying glasses. A group contains
one or several points or groups. The plus sign (+) to the left of a group
expands the contents and a minus sign (-) collapses the group.
It is required that the operator has at least a basic knowledge about how
Idefix is used, it is not covered here.
Figure 5. The full test plan with no points or groups hidden.
When the InitTestEnvironment group has been run, depending on the

configuration done, some groups may be hidden.
Ex: The test object contains 2 magazines and NO Site Controller, the
SiteController, Mag3.Test and Mag4.Test groups will be hidden and not
performed.
Ericsson Internal

When the test is started in auto mode, the test plan will start to execute from
the top. If the test is started in manual mode, the operator must start the test
manually by right clicking on the desired test point/group and choose
adequate action.
4 Running the test plan

This is the sequence which the tests will be executed.
4.1 InitTestEnvironment
Figure 6. The InitTestEnvironment test group expanded.
This group must always be launched before anything else can be done. The
purpose is to:
Ericsson Internal

• Check for previous runs in Testnet, if one exists a reason should be

given by the operator.
• Initialize the CTS API.
• View test instructions in an Idefix tab.
• Collect information about the current test object.
• Flush the ARP table on the CTS IPU client’s Node Network interface.
• Configure the CTS IPU client’s Node Network interface for CSM 2.0.
• Reset the CTS switch and use default settings during test.
• Reset of VMWare to ensure no virtual machines are running. i.e

VMWare player should not be running when testing CSM 2.0.
• Create connections to be able to communicate with the test object.
The PowerSupplyControl_OFF and all the TST2Setup will run simultaneously.

The same applies to PowerSupplyCOntrol_ON and CreateConnections. This
is done because they are independent to each other and will save time in start
up process.
The TestInstruction testmethod will create a tab in Idefix which will contain the
1521 document for CSM. The instructions can be accessed throughout the
whole test by pressing the tab called ‘Test Instructions’.
When the test method ‘DefineNode’ is performed, the cabinet serial added in
the beginning of the test will be compared to the record in bartrack. An dialog
will then appear as illustrated below:
Ericsson Internal

Figure 7. The node and order definition dialog.
A few choices can be done. For some products there might be less choices
since some controls will be locked to avoid any accidental misconfiguration
from the operator. Described from top:
Ericsson Internal

• CTS Power And TS2T

- This should be checked if the test is performed in a CTS Neptune
environment which is the normal case. If unchecked, manual power
control and configuration of the network is required. By default the box
is checked if the program is run on a CTS station with ID 2700-2799.
(At the Katrineholm site, production CTS stations starts from 2700 and
up, lab CTS stations starts at 2799 and down)
• Production Environment
- Normally checked, otherwise the automatic QSP, BarTrack and test
report will NOT be performed. By default the box is checked if the
program is run on a CTS station with ID 2700-2799. (At the
Katrineholm site, production CTS stations starts from 2700 and up, lab
CTS stations starts at 2799 and down)
• Cabinet Present
- Check this box if the current test object contains a cabinet, uncheck if
the test object only consists of a magazine. The picture to the right will
change accordingly.
• Site Controller Present

- Check this box if the current test object contains a Site Controller,
uncheck if the test object does not contain an ESC. The picture to the
right will change accordingly. The checkbox for ‘Cabinet Present’ must
be checked in order to check this box.
• Number of TLI boards is automatically set to the amount of TLI boards

in the BOM. The picture on he right side will then use this value to
determine how many magazines to show.
• Order And Test Report Info -boxes

- Fill in these boxes with the proper data for the current test object.
The normal situation is that the started Idefix program will be filled in
as the product number along with the scanned serial number. If the
program is started from Visual Studio or in another abnormal way, no
product number will be filled in. In that case the dropdown will contain
all valid products.
During/after the transfer to the ONE system, internal and purchase

order number can change name on order documents as follows:
internal order name = production order number

purchase order number = sales order number
The dialog will accept both formats.
• OK & Abort
- OK will make the test proceed; abort will exit the dialog and end the
whole test with a ‘Fail’ result.
Ericsson Internal

The dialog will as far as possible setup the form with the static info
corresponding to the selected product. The operator must always validate that
the defined node is identical to the real node since dynamic product structures
exists along with the static products in the CSM20 family.
4.2 The virtual cabling instruction
The reference [3] points to the paper version of the cabling instruction; this
information is also displayed in a virtual cabling instruction as shown below.
All shown cables MUST be connected before continuing the test. Cables not
visible in the virtual cabling instruction should not be connected; this is the
case when an ESC is missing.
Ericsson Internal

Figure 8 The virtual cabling instruction
4.3 Start.PowerSupplyControl_ON
This test point will power on the whole test object, either automatically or
prompt the operator to do it manually depending on what has been chosen in
the ‘DefineNode’ dialog. All CPFU boards and, if exist, ESC should be
powered on. If power cables are misplaced according to the cabling
instruction, on
e or more CPFUs may now not have any power supplied.

Ericsson Internal

4.4 SiteController.Test
Figure 9. The Site Controller test expanded.
If an ESC is defined to be present in the test object, the following will be performed:
• LoadESCImage requests an USB flash stick to be inserted in the ESC. The ESC
will automatically start to load the image when the stick is inserted into a bricked
ESC. It is wise to have the stick inserted before the test is started to save some
time. There is to the other hand no problem to insert it later when prompted for in
the dialog.
• ReadESCPID issues a command towards the ESC which in return responds with its
hardware ID (PID) data which is validated to be in a useable format. The Data is
saved in program memory in a virtual node once it has been validated with
Bartrack.
• VerifyConnectionToCSM is used to verify the cables and position of the DENIB

chain. A command is performed on the ESC which makes each CMB to respond.
Since each magazine contains two CMBs the result is easily interpreted.
• SiteControllerPowerRedundancy is used to verify the power cables and the power

inlets to the ESC. First inlet A is shut off, the ESC is communicated with, then
power is restored. The same will then be performed with the B inlet.
• ResetESCToBrickMode will prompt the operator to remove the USB flash stick. The
ESC will then begin to reset it self to brick mode which is the state to deliver the
ESC in to customer.
Ericsson Internal

The test of the ESC requires an ethernet cable to be connected and the USB flash
stick to be inserted as described in the cabling instruction.
NOTE: The ESC will double flash with the green LED for a few minutes after the stick
has been removed, this will not affect other tests for CSM but the power must not be
removed during this double blink.
After these tests, the ESC is stated as tested and no more communication will be done
towards the device.
4.5 ReadMagazineData
The purpose of this test point is to collect data from each magazine. Since no
ID prom is present in the magazines to be read, the operator must manually
submit the Serial Numbers for all subracks in the Node. The operator will be
presented with the dialog below:
Ericsson Internal

Figure 10. The dialog used for collecting magazine HW ID data.
The previously defined node will yet again appear and an arrow will be
pointing on the magazine to submit data from. The requested data is the
magazine Serial Number.
The easiest way to get the magazine serial number is by using the scanner,
which setting the scanner has does not matter. Make sure the textbox
focused is empty before scanning. Once a serial has been scanned a
comparison with bartrack will be executed to see if the hardware scanned
matches the entries in bartrack. If the serial turns out OK, a check icon will be
shown and the OK button will be enabled.
There will be a validation on all data submitted; also it is impossible to double

submit data.
Ericsson Internal

When the OK button is clicked the arrow will move upwards if more than one
magazine is present, otherwise the dialog will exit. All data is saved in the
virtual node to be used in QSP, BarTrack and to be written to the flash on
each accompanying CMB pair.
Clicking ‘Abort’ will exit the dialog and end the whole test with a ‘Fail’ result.
4.6 MagX.Test
These tests are identical for each magazine and may not be present
depending on the node defined earlier. The magazine located in the bottom is
stated as the first and therefore Mag1, the second is the one above (Mag2)
and so on. The test will always start with the two ethernet cables connected to
the CMBs in Mag1 (as described in the cabling instruction). When the first
magazine is finished, a dialog is displayed prompting the operator to move the
cables to the next magazine until all magazines have been tested. The test
does the following:
Figure 11. One of the magazines test plan expanded.

Ericsson Internal

• MagX.ReadBoardData issues a command on the Working CMB which

responds with its magazine’s boards HW ID data. The data is used for
QSP, BarTrack and test report and stored in the virtual node. When
valid data has been read, each TLI is verified to be of the same type.
No mix between balanced/unbalanced TLIs is allowed in one
magazine. The board data will be compared to bartrack and the BOM
entries, to see if the right kind of blade and that the right amount of
blades have been installed.
• MagX.PowerRedundancy is performed in the same manner as for the

ESC. Power is shut off to the CPFU-A board and a check is done to
verify that the CSM magazine is still responding, power is restored and
shut off to CPFU-B and an alive-check is yet again performed.
• MagX.TrafficTestProtectingCMB performs a traffic test which purpose

is to test the backplane and each board’s interconnection. See Figure
6 below. Traffic is generated on a TLI board and looped in the Working
CMBs STM-1 port. Path is:
TLIx -> bplane -> WCMB -> bplane -> PCMB -> loop -> PCMB ->
bplane -> WCMB -> bplane -> TLIx.
Map is: TLI1 -> CMB port A… TLI4 -> CMB port D.
• MagX.TrafficTestWorkingCMB performs a traffic test which purpose is

to test the backplane and each board’s interconnection. See Figure 7
below. Traffic is generated on a TLI board and looped in the Working
CMBs STM-1 port. Path is: TLIx -> bplane -> PCMB -> bplane ->
WCMB -> loop -> WCMB -> bplane -> PCMB -> bplane -> TLIx.
Map is: TLI1 -> CMB port A… TLI4 -> CMB port D.
• MagX.CheckSFPOpticalPlugs simply checks that the test loop plugs

have been removed and replaced with the SFP-optical plugs which
should be delivered with the node. Validation also checks that plugs
are inserted in correct ports if the subrack contains less than four TLI
boards. Test cannot continue unless proper plugs are sensed.
• ClearSettings is used to reset the CMBs to the state before setup for
traffic test was done. The environment variables are reset and some
network parameters is set again.
• MagX.SaveMagDataToCMB saves the previously collected magazine

data to both CMBs’ flashes.
• MagX.RebootSystem will perform a simultaneous reboot of both

CMBs and validate that the system boots up properly with correct
network parameters.
• ConnectNextMagazine is prompting the operator to move the Ethernet

cables connected to the CMBs if another magazine in the same
cabinet is to be tested. If this is the last magazine no action will done.
Ericsson Internal

• MagX.FlushARPTable is necessary since the next pair of CMBs will

have the same IP address but different MAC addresses. This can
cause strange networking problems if not performed.
Figure 12. Traffic test setup for Protecting CMB.

Ericsson Internal

Figure 13. Traffic test setup for Working CMB.
4.7 BarTrackNode
This test method connects the child items serialnumber in the node to the
parent cabinets serial.
4.8 HWInventoryToQSP
This test method will collect all previously HW ID data and upload it to QSP.
There is a validation that QSP accepts the file as well.
4.9 End.PowerSupplyControl_OFF
This method will automatically power off the whole test object if the test
environment supports it, otherwise the operator will be prompted to do it
manually.
4.10 GenerateTestReport
After test a test report will be generated based on the tests performed and
node defined. A dialog will precede the printing, prompting for a printer to be
used as shown below:
Ericsson Internal

It is possible to print several copies of the report as long as the test program
has been executed before. If the paper test report ‘disappears’, an electronic
copy is saved as a blob and can be fetched from Testnet when the test
program is finished. First line support should be addressed in that case.
Problems installing printer, finding a printer or printing trouble should be

addressed to the IS/IT-responsible/platform personnel since this test program
is using the standard Windows printing mechanism.
4.11 CleanUp
After test all connections need to be killed and the resources allocated by the
CTS API will be released. If the clean up is not performed and Idefix is just
terminated in any other way, each connection tab will leave a ‘tail –f’-process
and a ‘bash’-process running. These can be killed manually by accessing the
‘Windows Task Manager’, tab Processes.
4.12 SaveBlobs
This method will upload all test logs, a digital copy of the test report and all
communication logs to Testnet.
4.13 Todo after the test
Since the test program will prompt for removal of the SFP test plugs from the
CMBs and insertion of the SFP-to-optical plugs right after the traffic test, this
step should already have been done. For clarity, this is what should be done:
If order contains SFP-optical plugs, they should be inserted in the CMBs and
delivered that way to the customer. If magazine contains less than four TLIs,
begin to equip the CMBs from port A. Throw away the plastic boxes that the
plugs came in.
Example: Magazine contains TLI1 and TLI2 only, insert plugs into port A and
B on both CMBs in that subrack.
Sign off the test report.
5 References
[1] 1/1523-FAP 130 2050 "Empty Factory Test Report”
[2] EAB-09:026034 Usv “QSP submitting and format converter”
[3] 5/1074-LTM 187 05/1 “CSM20 cabling instruction for CTS”
[4] 19089-CYA 901 1338/1 “CSM20 CTS Function Module”
Ericsson Internal

6 APPENDIX
6.1 Login to devices
CMB_W: 10.10.64.200:23/16
CMB_P: 10.10.64.201:23/16
ESC: 10.10.64.202:22 user:oss pass:default
6.2 Sign off and Distribution of the test report
The test report should be printed after test and signed by the tester/operator.
If printing fails for any reason, an empty template can be fetched from
reference [1]. The test report can also be printed directly to a PDF document
and printed later when the printing environment is restored.
This procedure is left to the production organization to decide in detail.
6.3 Paths relevant for the test
QSP dump path:

\\Eemea.ericsson.se\esekhdfs01\GroupKH\Dagligt\QSP_nod\PN\CSM\TEST
CSM2\
CSM node test logs: (printouts from CMBs)

C:\Data\ITP\External\CTS\CSM\Logs\
CTS system logs:

C:\Data\ITP\External\CTS\Logs\
6.4 CSM 2.0 support and knowledge
An ERICOLL area for CSM2.0 is planned in the future. This chapter will be
updated when it is in place.
6.5 Quick cabling instruction
Full details see ref [3].
For node in cabinet, connect:
• CDEV0 – A4 (if exist)

Ericsson Internal

• CDEV4 – A0
• CDEV5 – A1
To magazine 1:
• CMB_W – CTS switch port 1 (include sfp-rj45 adapter)
• CMB_P – CTS switch port 2 (include sfp-rj45 adapter)
• ESC port 1 - CTS switch port 2 (if exist)
• Equip all 8 CMB STM-1 ports with loop plugs.
For expansion magazine connect:
• CPFU-A – A1
• CPFU-B – A2
• CMB_W – CTS switch port 1 (include sfp-rj45 adapter)
• CMB_P – CTS switch port 2 (include sfp-rj45 adapter)
• Equip all 8 CMB STM-1 ports with loop plugs.

1 1521-Fap1302050eng

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1 1521-Fap1302050eng

Uploaded by

Copyright:

Available Formats

Ericsson Internal

TEST INSTRUCTIONS 1 (23)

EAB/FPR/CN ERAKNML Mikael MK Karlsson 1/1521-FAP 130 2050 Uen

EAB/FPR/CN Per E Larsson 2013-02-01 G

CSM2.0 automated node test in CTS environment

Version Date Adjustments

EAB/FPR/CN ERAKNML Mikael MK Karlsson 1/1521-FAP 130 2050 Uen

EAB/FPR/CN Per E Larsson 2013-02-01 G

4.11 CleanUp ................................................................................... 21

1.1 Hardware requirements

This test program requires a CTS Neptune hardware of revision R1D or

A printer connected to the CTS Neptune or connected to the ECN which is

1.2 Software requirements

EAB/FPR/CN ERAKNML Mikael MK Karlsson 1/1521-FAP 130 2050 Uen

EAB/FPR/CN Per E Larsson 2013-02-01 G

2 CSM 2.0 node and magazine overview

• An empty magazine contains 2 CPFU boards and 2 CMB boards. This

• An equipped magazine always contains 1-4 TLI boards. The

• TLI boards can be of two types, balanced or unbalanced. There is no

• Board and port numbering as shown below:

Figure 1. A CSM2.0 magazine with port and board definitions.

3 Automated Node Test

EAB/FPR/CN ERAKNML Mikael MK Karlsson 1/1521-FAP 130 2050 Uen

EAB/FPR/CN Per E Larsson 2013-02-01 G

3.1 Control 48V CTS power and configuration of CTS Neptune

The automatic configuration of the CTS Neptune is:

• Setup of the network interface for ‘Node Network’-interface.

• Setup of the CTS Neptune Switch.

• Killing any virtual machines running in VMWare. Since other test

• Flush of ARP table before each node and each magazine.

The configuration is automatically done in the Idefix program as test points.

3.2 The generic message box

EAB/FPR/CN ERAKNML Mikael MK Karlsson 1/1521-FAP 130 2050 Uen

EAB/FPR/CN Per E Larsson 2013-02-01 G

Figure 2. Example of the generic message box used to inform operator.

3.3 How to start the test

Figure 3. The dialog when starting a new test.

EAB/FPR/CN ERAKNML Mikael MK Karlsson 1/1521-FAP 130 2050 Uen

EAB/FPR/CN Per E Larsson 2013-02-01 G

- If cabinet exists, scan/use serial in the cabinet frame. The

- If test object is an expansion magazine, the label to use is

Figure 4. Location of the main product label on an expansion magazine.

Example: A Katrineholm site serial is A061234567, if the ‘empty magazine’

EAB/FPR/CN ERAKNML Mikael MK Karlsson 1/1521-FAP 130 2050 Uen

EAB/FPR/CN Per E Larsson 2013-02-01 G

Figure 5. The full test plan with no points or groups hidden.

When the InitTestEnvironment group has been run, depending on the

EAB/FPR/CN ERAKNML Mikael MK Karlsson 1/1521-FAP 130 2050 Uen

EAB/FPR/CN Per E Larsson 2013-02-01 G

4 Running the test plan

Figure 6. The InitTestEnvironment test group expanded.

EAB/FPR/CN ERAKNML Mikael MK Karlsson 1/1521-FAP 130 2050 Uen

EAB/FPR/CN Per E Larsson 2013-02-01 G

• Check for previous runs in Testnet, if one exists a reason should be

• Initialize the CTS API.

• View test instructions in an Idefix tab.

• Collect information about the current test object.

• Reset of VMWare to ensure no virtual machines are running. i.e

• Create connections to be able to communicate with the test object.

The PowerSupplyControl_OFF and all the TST2Setup will run simultaneously.

EAB/FPR/CN ERAKNML Mikael MK Karlsson 1/1521-FAP 130 2050 Uen

EAB/FPR/CN Per E Larsson 2013-02-01 G