Professional Documents
Culture Documents
CTD Preparation Tips
CTD Preparation Tips
CTD Preparation Tips
• Cautious: Not allow to open new browser tab during exam. Close it
immediately if accidentally opened.
Virtual Machine Environment
• Supported shortcut keys
• Copy paste
• TestStand supported shortcut keys
• F2 – Rename or Edit value of selected cell
• Ctrl + Space – Auto complete
• Tab – Go to next focus control
• Ctrl + D – Close opened report
• Ctrl + F5 or F5 – Run sequence
• F8, F10 – Step Into and Step Over during debugging
• Probably could use F9 – Toggle breakpoint on selected step
• Other than these, you may try out yourself
• Can find out more TestStand shortcut keys from here and here
Virtual Machine Environment
• Your CTD exam materials will be on desktop exam folder. It contains:
• Exam paper in PDF file
• An executable to package your answer into zip file
• Instruction of using the executable is in the exam paper. Basically,
when run the executable:
• You are asked to provide path to your sequence file.
• You are asked to provide the destination of the exported zip file location
• So, it means you can write your sequence in any place, and it will export to
the destination you specified.
• To be safe, just follow the path shown in screen shot picture in the exam paper.
Virtual Machine Environment
• The zip file packaged by the executable will contain:
• Your sequence file
• Some TestStand station configuration files (such as GeneralEngine.cfg) to
prove you are using settings required in the exam question. Example:
Virtual Machine Environment
• Therefore, when you finish the solution:
• Make sure the station settings and result processing
settings follow the requirements in the exam
questions.
• Close the sequence file and run the executable to
package the zip file.
• Can unzip to check the contents are not corrupted.
• Tell the proctor where is your location of the zip file.
Virtual Machine Environment
• The displayed screen size in virtual machine is quite limited. Probably
related to your laptop/computer screen size as well.
• Unfortunately you cannot use extended monitor.
UI Configuration
Default:
Large:
Hit Enter
Example:
• Locals.Array ➔ Your array to append to
• Locals.Index ➔ Location to add
• Locals.Num ➔ The value you insert
Allocate Array Size
1D Array: PropertyObject.SetNumElements ( numElements, options = 0)
• ProcessSetup
• Run only once at the very beginning of a Test
UUTs / Single Pass.
• Used for initializing hardware or variable that
needs to be done once
• MainSequence
• Your main part of your code. This is repeated for
Test UUTs
• UUT initialize and close can put into the Setup &
Cleanup step group
Show Your Understanding of Code Modularity
MainSequence
ProcessSetup ProcessCleanup
(Repeated)
• ProcessCleanup
• Run only once at the very end of a Test UUTs /
Single Pass.
• Used for closing hardware or release the
reference that needs to be done once
Show Your Understanding of Code Modularity
• Normal subsequence
• Define the sub-sequence parameters in order to
pass value from caller sequence
Caller Sequence: MainSequence • You can also use FileGlobals to pass variable which is
global to the sequence file (such as device session)
Sub-Sequence: Test
Example Use of Sub-Sequence
From CTD Sample Exam:
Note:
In exam, it may not list the steps in each test group repeatedly as seen
on the right. It may only list once and ask for repeating the test for
different conditions. Read the test specifications carefully!
Other Guidelines
Other Guidelines
• Any difference in the structure of the question from CTD sample
exam?
• Quite similar, no much difference.
• Even the power supply and DMM APIs are quite similar to CTD sample exam. But should
read them carefully.
• The device operation may presented in a state diagram. Make sure you know
how to read.
Other Guidelines
• Tips to familiarize with the question and code modules quickly?
• The device under test is likely something you can find in your surrounding
(like a panel washing machine, etc). Its operation is not hard to imagine.
• So, before getting into any detail, use your common sense to visualize in your
mind how the device operates by looking at its inputs/outputs.
• You can start from the device connection diagram
• Once you have clear a image, then confirm your imagination by looking at the
details. Human are good at noticing the difference!
• Draft your test sequence using Label step type first, so you can get the full
picture of the flow.
• The code module are quite straight forward to the test specification. So no
need to read all the APIs in detail before writing code. Just skim them through
first.
Other Guidelines
• Anything else?
Practice
makes
Perfect!
*Don’t do it only last minute
;-)