TDE
/
tdelibs
mirror of https://mirror.git.trinitydesktop.org/gitea/TDE/tdelibs
0
0
Fork 0
Code Issues Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '147f714fe7'
${ noResults }
tdelibs/dcop/tests
History
Slávek Banko efae38628b
tests: Wait for the dcop server to be ready. 		4 years ago
..
CMakeLists.txt cmake: Avoid double generating of dcop/tests files. 5 years ago
Makefile.am Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. 15 years ago
README Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. 15 years ago
driver.cpp Make dcop tests run without X 7 years ago
driver.h Trinity Qt initial conversion 15 years ago
generate.pl dcop/tests: run dcop tests in a safer manner 7 years ago
run-tests.sh tests: Wait for the dcop server to be ready. 4 years ago
test.cpp Make dcop tests run without X 7 years ago
testcases Add dcop tests to cmake 7 years ago

README 

WHAT IS IT
==========

This is a test case for the dcop family of utils.


HOW TO USE IT
=============

testcases is the important file, the rest is build system.
It details what functions we should generate and with what arguments to call them

'make'ing will generate a small dcop app which runs in two modes: the batch mode and the
interactive mode. The batch mode simply runs all the tests inside the app, while in the interactive
mode, the app goes to sleep and exactly the same tests are called from the outside. Should the results
differ, we probably have a bug.


HOW IT WORKS
============

Six files get generated:

                             local               external           shell
                       +-------------------+-----------------+-----------------+
                       |                   |                 |                 |
   stdout              |   batch.stdout    |   dcop.stdout   |  shell.stdoud   |
                       |                   |                 |                 |
                       +-------------------+-----------------+-----------------+
                       |                   |                 |                 |
   return values       |   batch.returns   |   dcop.returns  |  shell.returns  |
                       |                   |                 |                 |
                       +-------------------+-----------------+-----------------+

The local column are the files generated in batch mode where the calls are made locally, the external and shell columns lists files made using dcop calls, "external" calls were made through an external program and shell call were made using the dcop shell client. The stdout row is what got printed to stdout and the returns row is what return values the various functions support. These are kept separate to simplify things.