Tdriver on Windows Installation notes

Tdriver Introduction

Nokia will focus on providing a general development interface with QT, so that developers can develop applications and services for mobile devices and desktop systems in a unified manner. Qt tries its best to create applications that can run on both mobile devices and desktop systems. Developers can use C ++/JavaScript & html/qml to develop software.

Testability Driver (TdriverIs a test tool open-source by Nokia. It allows automated testing of QT applications to run on any platform (of course, any platform supporting QT, such as Linux/Windows/MAC/Symbian/maemo/meego ).

PS: the CE/Qt-embedded line does not work. (Reprinted please keep the source, ye xunkai, QQ: 939849)

System Structure

Necessary tools

• Qt 4.7.4 or later (one of the compilation environments, we recommend that you use the full version 4.7.4, which comes with the mingw compiler and does not need to be installed separately)
• Ruby 1.8.7-p72 or later)
• Msysgit (tool for getting tdriver code, Windows)
• Mingw (compiler tool chain)

Procedure

1. Install QT
   (Red frame part: http://qt.nokia.com/downloads)

   Directory after installation

2. Install Ruby
   Http://rubyonrails.org/download)

3. Install msysgit
   Http://code.google.com/p/msysgit/downloads/list)

4. Set Environment Variables
   (Mingw/QT/Ruby/tdriver)

   <Mingw> \ bin
   <QT> \ bin
   <Ruby> \ bin
   <Tdriver drive root> \ qttas \ bin
   <Tdriver drive root> \ qttas \ Lib
   <Tdriver drive root> \ tdriver/visualizer

   Note:
   * The whole % PATH % should not contain spaces, otherwise the mingw tool will not work like mingw32-make! However, if the source code of QT is long paths, the compiled library is normal.
   * Do not add the GIT bin to % PATH %. Otherwise, qmake mistakenly assumes that it is a POSIX system and generates a POSIX makefile instead of a Windows makefile.
   And output it to the GIT directory as/rather than \ qttas.

5. Get code
   (Run the following command in git Bash to get the code to the current directory. Experience: it is much more efficient to use command lines than to use graphical windows)

   Git clone git: // gitorious.org/tdriver/driver.git
   Git clone git: // gitorious.org/tdriver/sut_qt.git
   Git clone git: // gitorious.org/tdriver/agent_qt.git
   Git clone git: // gitorious.org/tdriver/visualizer.git
   Git clone git: // gitorious.org/tdriver/tests.git

7. Component Installation
   (Agent_qt, driver, sut_qt, visualizer, tests)

   * Agent_qt

   CD agent_qt
   Git checkout 0.9.2
   Qmake config + = debug-R & mingw32-make debug install
   CD ..

   * Driver

   Git checkout 0.9.2
   Update. bat
   CD ..
   (Note: <Ruby> \ Lib \ Ruby \ gems \ 1.9.1 \ gems \ testability-driver-1.3.2.20111009110440 \ Lib \ tdriver \ base \ test_object, #103 lines, there will be character set processing errors, you must manually delete spaces to run properly .)

   * Sut_qt

   CD sut_qt
   Git checkout 0.9.2
   Update. bat
   CD ..

   * Visualizer

   CD visualizer
   Git checkout 0.9.2
   Qmake config + = debug-R & mingw32-make debug install
   CD ..
   (Note: by default, visualizer is installed in c: \ tdriver ?? Strange)

   * Tests

   CD tests
   Git checkout 0.9.2
   Qmake config + = debug-R & mingw32-make debug install
   CD ..

8. Run

   Controlled end service: qttasserver
   Controlled terminal manager:Qttas_ui

   Remote control end:Tdriver_visualizer (connect to the controlled end by full refresh)

9. Checkpoint: whether the applet can be controlled

   Enter calculator for trial run. The small frame is the remote control area and the large frame is the actual program.

   
   

(Reprinted please keep the source, ye xunkai, QQ: 939849)