• Publication

• [1] M. Lahami, F. Fakhfakh, M. Krichen, and M. Jmaiel. Towards a TTCN-3 Test System for Runtime Testing of Adaptable and Distributed Systems. In The 24rd IFIP International Testing Software and Systems Conference (ICTSS) Proceedings, Lecture Notes in Computer Science. Springer, 2012.
• [2] M. Lahami and M. Krichen. Test Isolation Policy for Safe Runtime Validation of Evolvable Software Systems. In the 22nd IEEE International Conference on Enabling Technologies: Infrastructure for Collaborative Enterprises (WETICE), Hammamet, Tunisia, June 17-20, 2013.

• Contact

  • Address: 
        Mariam LAHAMI
        ReDCAD - DGIMA - ENIS 
        Route de la Soukra km 3.5
        B.P. W 1173 Sfax - Tunisia

    Phone/Fax:
        +216 74 666 578 

    Email:
     mariam.lahami@redcad.org

     

In order to detail the internal interactions in TT4RT system, this workflow is given:

• When a reconfiguration action is triggered, the test plan that describes the affected parts of the SUT by this dynamic change and the test configuration used to validate it, is generated. This plan is considered as an input to the TT4RT system (Step 1).
• Test isolation policy is called for each component under test in order to choose the best test isolation technique (Step 2).
  
• The appropriate test isolation technique is then used to prepare the test environment (Step 3).
  
• After preparing the test environment, the test system user initiates the test execution through the TTmanGUI and by calling the adequate method in the TM entity TciStartTestCase (Steps 4-5).
  
• Once the test process is started, the TE entity creates the involved test components and informs the SA entity that the test case has been started with the aim of allowing the SA entity to prepare its communication facilities. This is done through the call of triExecuteTestcase method (Step 6).
  
• Next, TE invokes the CD entity in order to encode the test data from a structured TTCN-3 value into a form that will be accepted by the SUT. This is done through the call of encode method (Step 7).
  
• The encoded test data is passed back to the TE entity as a binary string and forwarded to the SUT via the SA entity with the triSend method (Steps 8-9-10).