Difference between revisions of "Testing your application"

From NAMIC Wiki
Jump to: navigation, search
 
(2 intermediate revisions by the same user not shown)
Line 2: Line 2:
  
 
== Testing procedure ==
 
== Testing procedure ==
 
+
* '''Make sure your LD_LIBRARY_PATH (Linux) or PATH (Windows) contains the absolute path for NaviTrack library (libNaviTrack.so on Linux, and NaviTrack.dll on Windows)'''
 
* Download the config files in the previous page: '''Send.txt''' and '''Receive.txt''' (you can rename them as xml files but it's not necessary)
 
* Download the config files in the previous page: '''Send.txt''' and '''Receive.txt''' (you can rename them as xml files but it's not necessary)
* On your computer, create two shell terminal windows
+
* On your computer, create two shell terminals (Linux) or command prompts (Windows)
* In both terminal, change directory ('''cd''') to your NaviTrack-build directory
+
* In both windows, change directory ('''cd''') to your NaviTrack-build directory
* In one terminal, run this:
+
* In one window, run this:
  '''./myapp send.xml'''
+
  '''./middleware Send.txt'''
 
  and then press 1
 
  and then press 1
* In the other terminal, run this command:
+
* In the other window, run this command:
  '''./myapp receive.xml'''
+
  '''./middleware Receive.txt'''
 
  and then press 1
 
  and then press 1
* Have the input focus for the terminal running the sending process. Press some keys on the keyboard (see next section) to generate simulated tracking data.  
+
* Have the input focus for the window running the sending process. Press some keys on the keyboard (see next section) to generate simulated tracking data.  
** You should see the data update in the other terminal (the receiving side)
+
** You should see the data update in the other window (the receiving side)
 
** All received data will be also saved into a file named '''file-out.txt''' in the same directory where you run your application
 
** All received data will be also saved into a file named '''file-out.txt''' in the same directory where you run your application
  

Latest revision as of 14:09, 18 May 2007

Home < Testing your application

Here comes the point you want to test how your application works. At this moment, we're not going to use any real tracking device; instead, we will use ConsoleSource, a built-in module in NaviTrack, to simulate the generation of tracking data.

Testing procedure

  • Make sure your LD_LIBRARY_PATH (Linux) or PATH (Windows) contains the absolute path for NaviTrack library (libNaviTrack.so on Linux, and NaviTrack.dll on Windows)
  • Download the config files in the previous page: Send.txt and Receive.txt (you can rename them as xml files but it's not necessary)
  • On your computer, create two shell terminals (Linux) or command prompts (Windows)
  • In both windows, change directory (cd) to your NaviTrack-build directory
  • In one window, run this:
./middleware Send.txt
and then press 1
  • In the other window, run this command:
./middleware Receive.txt
and then press 1
  • Have the input focus for the window running the sending process. Press some keys on the keyboard (see next section) to generate simulated tracking data.
    • You should see the data update in the other window (the receiving side)
    • All received data will be also saved into a file named file-out.txt in the same directory where you run your application

How to use ConsoleSource

On page 33 of this pdf file:
http://studierstube.icg.tu-graz.ac.at/opentracker/html/howto_opentracker.pdf you will find all possible functions and their default keys on your keyboard for using ConsoleSource.