> Sent: Wednesday, June 23, 2021 at 11:45 AM
> From: "Kai Köhne"
> To: "Jason H" , "interestqt-project.org"
>
> Subject: RE: [Interest] make check not working (macOS)
>
> HI Jason,
>
> It looks to me like you're trying to a
> > I want a brain-dead, simple, 0-maintenance test kit. The only thing the
> > developers should have to worry about is adding test implementations once
> > it is started.
> >
> > Can this be achieved in Qt?
>
> With Qt and QtTest, sure. But your question was "in qmake".
>
> The answer is also
On Wednesday, 23 June 2021 09:03:14 PDT Jason H wrote:
> So I have to manually maintain the modules being tested as a separate
> project? If so, that's pretty undesirable because of the manual effort to
> make sure that the test project is using the same source that the actual
> application uses.
On Wednesday, 23 June 2021 08:08:16 PDT Jason H wrote:
> When I run `qmake && make check` it just executes the main program
The test *is* the main program.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel DPG Cloud Engineering
> Sent: Wednesday, June 23, 2021 at 11:45 AM
> From: "Kai Köhne"
> To: "Jason H" , "interestqt-project.org"
>
> Subject: RE: [Interest] make check not working (macOS)
>
> HI Jason,
>
> It looks to me like you're trying to a
HI Jason,
It looks to me like you're trying to add a test case into your normal
application executable. Is that correct?
The canonical use of QTest is different: You create a separate project for the
tests, in a separate directory. If you e.g. check back on
Ok, I was missing Q_OBJECT
But then `make`:
*** No rule to make target `test_sqldatabase.moc.json', needed by
`ndx-poc-ui_metatypes.json'. Stop.
I don't know where these .json files fit in the Qt build process. I've never
had to worry about them before.
> Sent: Wednesday, June 23, 2021 at