qca test

Hello Brad,

Sorry for the late response.
I tried the test again, end up at:

make[2]: Entering directory
`/usr/local/my/Development/kde/qca/unittest/tls'
gcc   tlsunittest.o   -o tlsunittest
tlsunittest.o: In function
`TLSUnitTest::cleanupTestCase()':
tlsunittest.cpp:(.text+0x95): undefined reference to
`QCA::Initializer::~Initializer()'
tlsunittest.o: In function `main':
tlsunittest.cpp:(.text+0xe2): undefined reference to
`QCoreApplication::QCoreApplication(int&, char**)'
tlsunittest.cpp:(.text+0xf1): undefined reference to
`QObject::QObject(QObject*)'
<snip>

But again, I think that if you skip some test according to
the plugins
installed, the test suite should be re-run after each
plugin
installation, so it should be provided separately.

Best Regards,
Alon.
_______________________________________________
delta mailing list
deltalists.affinix.com
http://lists.affinix.com/listinfo.cgi/delta-affinix.com

On Saturday 14 July 2007 03:21, Alon Bar-Lev wrote:
> Hello Brad,
>
> Sorry for the late response.
> I tried the test again, end up at:
>
> make[2]: Entering directory
> `/usr/local/my/Development/kde/qca/unittest/tls' gcc  
tlsunittest.o   -o
> tlsunittest
> tlsunittest.o: In function
`TLSUnitTest::cleanupTestCase()':
> tlsunittest.cpp:(.text+0x95): undefined reference to
> `QCA::Initializer::~Initializer()'
> tlsunittest.o: In function `main':
> tlsunittest.cpp:(.text+0xe2): undefined reference to
> `QCoreApplication::QCoreApplication(int&, char**)'
> tlsunittest.cpp:(.text+0xf1): undefined reference to
> `QObject::QObject(QObject*)'
> <snip>
I'm not seeing this. Something is wrong with your build.
Are you using cmake or qmake/qconf?

> But again, I think that if you skip some test according
to the plugins
> installed, the test suite should be re-run after each
plugin
> installation, so it should be provided separately.
The test suite determines what to test at run-time (not
build time). What 
difference would the packaging make?

Brad

_______________________________________________
delta mailing list
deltalists.affinix.com
http://lists.affinix.com/listinfo.cgi/delta-affinix.com

On 7/14/07, Brad Hards <bradhfrogmouth.net> wrote:
> I'm not seeing this. Something is wrong with your
build.
> Are you using cmake or qmake/qconf?

qconf.

>
> > But again, I think that if you skip some test
according to the plugins
> > installed, the test suite should be re-run after
each plugin
> > installation, so it should be provided
separately.
> The test suite determines what to test at run-time (not
build time). What
> difference would the packaging make?

For each plugin the package can unpack the plugin, unpack
the test
suite, compile the plugin, compile the test suite and run
the test
suite.

Alon.
_______________________________________________
delta mailing list
deltalists.affinix.com
http://lists.affinix.com/listinfo.cgi/delta-affinix.com

On Saturday 14 July 2007 10:22, Alon Bar-Lev wrote:
> On 7/14/07, Brad Hards <bradhfrogmouth.net> wrote:
> > I'm not seeing this. Something is wrong with your
build.
> > Are you using cmake or qmake/qconf?
>
> qconf.
I'll give that a try.

> > > But again, I think that if you skip some test
according to the plugins
> > > installed, the test suite should be re-run
after each plugin
> > > installation, so it should be provided
separately.
> >
> > The test suite determines what to test at run-time
(not build time). What
> > difference would the packaging make?
>
> For each plugin the package can unpack the plugin,
unpack the test
> suite, compile the plugin, compile the test suite and
run the test
> suite.
You need to run the testing manually (see TestPlan).

There is nothing to be gained by just seeing the unit test
tests pass (because 
that doesn't actually tell you if the plugin is tested). 

Brad

_______________________________________________
delta mailing list
deltalists.affinix.com
http://lists.affinix.com/listinfo.cgi/delta-affinix.com

On 7/14/07, Brad Hards <bradhfrogmouth.net> wrote:
> You need to run the testing manually (see TestPlan).

Manual and automatic is the same.

> There is nothing to be gained by just seeing the unit
test tests pass (because
> that doesn't actually tell you if the plugin is
tested).

I think you should not skip tests if relevant plugin is
available, so
running the same test suite will produce failures if
existing
components do not behave as expected.

Alon.
_______________________________________________
delta mailing list
deltalists.affinix.com
http://lists.affinix.com/listinfo.cgi/delta-affinix.com

On Saturday 14 July 2007 19:40, Alon Bar-Lev wrote:
> On 7/14/07, Brad Hards <bradhfrogmouth.net> wrote:
> > You need to run the testing manually (see
TestPlan).
>
> Manual and automatic is the same.
No, it isn't.

The difference between doing "make test" and
checking if the test pass, and 
running tests as described in TestPlan is important.

> > There is nothing to be gained by just seeing the
unit test tests pass
> > (because that doesn't actually tell you if the
plugin is tested).
>
> I think you should not skip tests if relevant plugin is
available, so
> running the same test suite will produce failures if
existing
> components do not behave as expected.
The test tries to determine if the plugin is available. If
the plugin is 
available, it runs the test for that plugin, and if the
plugin is not 
available, the test is skipped.

The problem is when the plugin should be available, but
isn't found for some 
reason. That is why the TestPlan needs to be run, and some
manual checks 
done.

Brad

_______________________________________________
delta mailing list
deltalists.affinix.com
http://lists.affinix.com/listinfo.cgi/delta-affinix.com

On Saturday 14 July 2007 03:21, Alon Bar-Lev wrote:
> make[2]: Entering directory
> `/usr/local/my/Development/kde/qca/unittest/tls' gcc  
tlsunittest.o   -o
> tlsunittest
> tlsunittest.o: In function
`TLSUnitTest::cleanupTestCase()':
> tlsunittest.cpp:(.text+0x95): undefined reference to
> `QCA::Initializer::~Initializer()'
> tlsunittest.o: In function `main':
> tlsunittest.cpp:(.text+0xe2): undefined reference to
> `QCoreApplication::QCoreApplication(int&, char**)'
> tlsunittest.cpp:(.text+0xf1): undefined reference to
> `QObject::QObject(QObject*)'
> <snip>
I'm not seeing this. For some reason, your code isn't being
linked correctly.

When I use qconf/qmake, I see this:
cd tls/ && /opt/qt43/bin/qmake tls.pro -unix -o
Makefile

cd tls/ && gmake -f Makefile

gmake[2]: Entering directory
`/home/bradh/coding/kdesupport/qca/unittest/tls'

/opt/qt43//bin/moc -DQT_NO_DEBUG -DQT_CORE_LIB -DQT_SHARED 
-I/opt/qt43/mkspecs/default -I. -I/opt/qt43/include/QtCore 
-I/opt/qt43/include/QtCore -I/opt/qt43/include
-I/opt/qt43/include/QtTest 
-I../../include/QtCrypto -I. -I. tlsunittest.cpp  -o
tlsunittest.moc

g++ -c -pipe -O2 -Wall -W -D_REENTRANT -DQT_NO_DEBUG
-DQT_CORE_LIB -DQT_SHARED 
-I/opt/qt43/mkspecs/default -I. -I/opt/qt43/include/QtCore 
-I/opt/qt43/include/QtCore -I/opt/qt43/include
-I/opt/qt43/include/QtTest 
-I../../include/QtCrypto -I.  -I. -o tlsunittest.o
tlsunittest.cpp

g++ -Wl,-rpath,/opt/qt43/lib -o tls tlsunittest.o   
-L/opt/qt43//lib 
-L../../lib -lqca -lQtTest -L/home/bradh/coding/qt-copy/lib
-L/opt/qt43//lib 
-pthread -pthread -lQtCore -lz -lm -pthread -lgthread-2.0
-lrt -lglib-2.0 
-ldl -lpthread

(test -z "" || cd "" ; targ=`basename
tls`; objcopy --only-keep-debug "$targ" 
"$targ.debug" && objcopy --strip-debug
"$targ" && objcopy 
--add-gnu-debuglink="$targ.debug"
"$targ" && chmod -x
"$targ.debug" ) ;

gmake[2]: Leaving directory
`/home/bradh/coding/kdesupport/qca/unittest/tls'

I can only suggest that you try cleaning your build and
reconfiguring / 
rebuilding.

Brad

_______________________________________________
delta mailing list
deltalists.affinix.com
http://lists.affinix.com/listinfo.cgi/delta-affinix.com