1 / 6

Tester #2 sleeping

Model. Listening Port #1= ip:tcp1. Tester #1 ready. Listening Port #2= ip:tcp2. Create Connect Start Behavior #1. Tester #2 sleeping. Create Connect. System Under Test. MTC. Create Connect. Tester #X sleeping.

kaloni
Download Presentation

Tester #2 sleeping

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Model Listening Port #1= ip:tcp1 Tester #1 ready Listening Port #2= ip:tcp2 Create Connect Start Behavior #1 Tester #2 sleeping Create Connect System Under Test ... MTC Create Connect Tester #X sleeping • Main Test Component: one MTC to create X PTCs. Parameter X is run-time configurable (in configuration file). • X PTC: ready to manage an incoming request. Initially only one PTC is listening the port but all the test components are deployed.

  2. Model CER CEA (1) (2) Tester #1 ready Listening Port #2= ip:tcp2 • System Under Test send a CER to the Test System using the first port, for example. • PTC Tester #1 answer with a CEA and continues in ready state listening for CCR messages. Create Connect Start Behavior #1 Tester #2 sleeping Create Connect System Under Test ... MTC Create Connect Tester #X sleeping

  3. Model CCR (3) Tester #1 busy Listening Port #2= ip:tcp2 (4) • System Under Test send a CCR to the Test System using the first port, for example. • PTC Tester #1 changes automatically its state from ready to busy, and wake up the next idle component, in this case PTC Tester #2 starting up Behavior #2. Create Connect Start Behavior #1 Tester #2 sleeping (5) Start Behavior #2 Create Connect System Under Test ... MTC Create Connect Tester #X sleeping

  4. Model CCA (7) Tester #1 busy Listening Port #2= ip:tcp2 • PTC Tester #2 now is ready to handle any incoming CCR while PTC Tester #1 is busy checking and answering to the CCR. Create Connect Start Behavior #1 Listening Port #1= ip:tcp1 Tester #2 ready Listening Port #2= ip:tcp2 (6) Create Connect System Under Test ... MTC Create Connect Tester #X sleeping

  5. Model Tester #1 sleeping (8) • Once PTC Tester #1 has sent the CCA to System Under Test it changes its status from busy to sleeping, and put into an idle mode until other PTC Tester wakes up again with Behavior #2 to handle potential incoming CCRs (in this case the load that the System Under Test is generating is not very heavy). Create Connect Start Behavior #1 Listening Port #1= ip:tcp1 Tester #2 ready Listening Port #2= ip:tcp2 Create Connect System Under Test ... MTC Create Connect Tester #X sleeping

  6. Model Tester #1 busy • In heavy load conditions all the PTC Tester components may be in a busy state that means no incoming message will be processes (the Test System is working in the limit). This situation is similar to the clipping phenomenon in analog amplifiers. The solution is simple: to increase the number of PTCs modifying the run-time X param. Tester #2 busy System Under Test ... MTC Tester #X busy CLIPPING!!!

More Related