Closed MartinDelille closed 4 years ago
I have no installation of Qt Creator, so I can't test. But my simple guess is that Qt Creator does not interpret the space between "is" and "empty" correctly. Assuming that Qt Creator runs ./BanditTest --only=is
, the first and the last test title match.
edit: What if you run --only=empty
?
edit2: To work around this problem in cases where you need many words to get the right result, you can use multple --only
arguments, like --only=is --only=empty
.
Yes using several --only
arguments works indeed in both case.
I noticed a difference with the
--only
parameter when runningbandit
in Qt Creator debugger.Given the following tests:
If I run it with
--only="is empty"
parameter, I have the following expected output:Unfortunately, passing the same parameter to the debugger doesn't behave in the same way:
Why is the spec
engine bmp display first frame
executed?I put the corresponding code here: https://github.com/MartinDelille/BanditTest
Strangely this problem happens only in Qt Creator debugger (not when starting the debugger from the command line).