djeedjay/boosttestui

GUI runner for boost.test

boosttestui's Issues

Feature request: copy test name

in the context menu of a test please provide a 'copy' to clipboard option, that copies the name of the text 'MotionSystemTest.ControllerConnectionLostThenRecover' to the clipboard from the test:

TEST_F(MotionSystemTest, ControllerConnectionLostThenRecover)

Also what could be nice, is 'copy cmdline' that would give me, for example:
MdlMotion2LibTest.exe --gtest_filter=MotionSystemTest.ControllerConnectionLostThenRecover

TestFixtureSetUp is not called in most recent version of BoostTestui (v1.1.5 from jan_17_2018)

    [TestFixtureSetUp]
    public void TestFixtureSetUp()
    {
        System.Console.WriteLine("C# TestFixtureSetUp");
    }

Here it works correctly in version 1.1.2

here it fails in 1.1.5:

reproduce:

namespace TestProjectNunit
{
    public abstract class FixtureBase
    {
        // This class has default constructor so it will generate an error
    }

    /// <summary>
    /// Simple sequences of Set and Get calls on the GFI interface.
    /// (no checks on received notifications etc.)
    /// </summary>
    [TestFixture]
    public class TestGFI03SetGet : FixtureBase
    {
        [TestFixtureSetUp]
        public void TestFixtureSetUp()
        {
            System.Console.WriteLine("C# TestFixtureSetUp"); // not called in v1.1.5
        }

        [TestFixtureTearDown]
        public void TestFixtureTearDown()
        {
            System.Console.WriteLine("C# TestFixtureTearDown");
        }

    }
}

Publish BootTestUi.exe file in next releases

Hi,

Can you please add the BootTestUi.exe file in the next releases ?

debugview++test 'LineBufferTest2' locks up the GUI temporarily

the test outputs 3x17.000 lines during the test, this completely locks up the UI while the test is running.
There is also another symptom visible:
a std::cout << msg << std::endl is not 'flushing' until the end of the test, so there is now way to tell the user to wait

Please add support for parameterized nunit tests

some tests don't load, because parameterized tests are not supported, see #27

https://github.com/nunit/docs/wiki/TestCaseSource-Attribute

Note: just noticed, there is already a pull request ready for this feature:
#25

Please merge it :)

Repeating tests will start a new process each time

For leak-tests it is useful to repeat tests 1000 or 10.000 times, however, to be able to monitor is the tests to no leak, it is needed that the --repeat option of the framework is used instead of re-starting the test by boosttestui.

DISABLED_ prefix not supported

From the 1.7 docs:

Temporarily Disabling Tests
If you have a broken test that you cannot fix right away, you can add the DISABLED_ prefix to its name. This will exclude it from execution. This is better than commenting out the code or using #if 0, as disabled tests are still compiled (and thus won't rot).

link: https://github.com/google/googletest/blob/d225acc90bc3a8c420a9bcd1f033033c1ccd7fe0/googletest/docs/AdvancedGuide.md

show the full path of a test somewhere

I other have multiple versions, debug/release/debug64/release64 in the recently opened list,
so it would be good if you could see which one is currently loaded, without having to re-load is again.

maybe in the title-bar? that would not make sense if we later decide to support loading multiple test projects

maybe in the hover- tooltip ?

When a DLL is reloaded because it is new and loading fails the old tests still remain visible

screenshop after [TextFixture] attribute was removed from the test, so the DLL has become invalid, the tests from the previous version of the DLL remain visible

Loading a nunit test dll gives 'no test cases'

This dialog is displayed if the [TestFixture] attribute is missing

[TestFixture]
public class Test
{
    [Test]
    public void TestMethod() 
    {
    }
}

I think it would be nice to suggest to check the [TestFixture] and [Test] attributes on the class and methods. Maybe add a code-example for nunit in the Help-menu also.

google test TEST_P icon stays grey when all tests are successful

Failing googletest shows as 'successful'

TEST(TestCase, Test)
{
	EXPECT_EQ(1 + 1, 2);
	throw std::exception("");
}

int main(int argc, char* argv[])
{
	testing::InitGoogleTest(&argc, argv);
	testing::InitGoogleTestGui(&argc, argv);

	return RUN_ALL_TESTS();
}

If the test fails to load it is not added to the 'Recent Tests'

reproduce: try to load an nunit test without the nunit framework dll present.
Also even if it was in the 'Recent Tests' already, it is removed, this is pretty annoying but typically you will want to fix the problem and load again.

Search / filter tests by name maybe SAIT feature?

ofter I know which test I want to run, but locating it in the long list can be a challenge. I would be nice to have either a search of filter feature on top of the list of tests.

Alternatively, a 'search as I type' feature like in debugview++ would also suffice.

google test type TYPED_TEST not supported yet?

see email

throwing an exception in a testcase seems to pass the test

The test is failing as the logging shows, but the UI checkbox is still marked 'green'

TEST(TestCase, Test)
{
EXPECT_EQ(1 + 1, 3);
}

TEST(TestCase, TestException)
{
throw std::exception("test");
}

TEST(DISABLED_TestCase, TestException)
{
throw std::exception("test");
}

int main(int argc, char* argv[])
{
testing::InitGoogleTest(&argc, argv);
testing::InitGoogleTestGui(&argc, argv);

return RUN_ALL_TESTS();

}

Feature request: load multiple tests

It would be nice to be able to open more then one test at the same time.
It would also be a unique feature, because I dont know of any other environment where you can load projects from different test-frameworks at the same time.

'&' characters in test messages are not printed

The ampersand is not printed but the following character is printed underlined.

some tests are not working

If the boosttestui is unable to query a list of tests, please show the stdout information in the output, this way the user can get feedback on why its not working

The case was a customized test that needed special commandline options and it was explaining this on the commandline but never shows in the boosttestui

Requested by fei users: a fixed spacing font in the text output

Test fails, but test runner shows it went fine

Test created using Google Test framework.

Unable to run a googletest that was not build with gtest-gui.h

I think this dialog is very nice, however, if I was to run someone else's tests it still be useful to continue.
Can we load anyway after pressing ok?

---------------------------
Boost Test Runner
---------------------------
Did you forget to #include <gtest/gtest-gui.h>?
---------------------------
OK   Help   
---------------------------

Proposal for new dialog: (and disable the 'attach debugger' button

---------------------------
Boost Test Runner
---------------------------
Did you forget to #include <gtest/gtest-gui.h>?
You can continue, but some functions will not be available.
---------------------------
OK   Help   
---------------------------

proposal: start a new project called MultiTestUI

since we now support

• boost
• googletest/googlemock-
• catch
• nunit
• and maybe soonish 'cppunit' (I will send an example)

Maybe rename the project

With nunit 2.6.7 or higher replaced TestFixtureSetUp and TestFixtureTearDown

1>C:\Users\jan\source\repos\Nunittest\Class1.cs(9,10,9,26): warning CS0618: 'TestFixtureSetUpAttribute' is obsolete: 'Use OneTimeSetUpAttribute'
1>C:\Users\jan\source\repos\Nunittest\Class1.cs(15,10,15,29): warning CS0618: 'TestFixtureTearDownAttribute' is obsolete: 'Use OneTimeTearDownAttribute'

// pre nunit 2.6.x TestFixtureSetUp syntax
namespace TestProject
{

    [TestFixture]
    public class Tester
    {
        [TestFixtureSetUp] // pre  2.6.x syntax
        public void TestFixtureSetUp()
        {
            System.Console.WriteLine("C# TestFixtureSetUp"); 
        }

        [TestFixtureTearDown] // pre  2.6.x syntax
        public void TestFixtureTearDown()
        {
            System.Console.WriteLine("C# TestFixtureTearDown");
        }

        [Test]
        public void Mytest()
        {
            System.Console.WriteLine("C# Mytest");
        }

    }
}

// nunit 2.6.x or nunit 3.x.x  replaced TestFixtureSetUp and TestFixtureTearDown
// with OneTimeSetUpAttribute and OneTimeTearDownAttribute

// TestFixtureSetUp and TestFixtureTearDown **are** still allowed, but reported as obsolete

namespace TestProject
{

    [TestFixture]
    public class Tester
    {
        [OneTimeSetUpAttribute ]       //new
        public void TestFixtureSetUp()
        {
            System.Console.WriteLine("C# TestFixtureSetUp"); // not called in v1.1.5
        }

        [OneTimeTearDownAttribute]     //new
        public void TestFixtureTearDown()
        {
            System.Console.WriteLine("C# TestFixtureTearDown");
        }

        [Test]
        public void Mytest()
        {
            System.Console.WriteLine("C# Mytest");
        }

    }
}

GoogleTest compatibility with parameterized tests is broken?

This works correctly in version 1.0.9.553 from september 8, 2016
but nolonger in 1.1.1 from 20 December 2016

Tested using googletest 1.8.0
(https://github.com/google/googletest/releases/tag/release-1.8.0)

#include "stdafx.h"
#include <gtest/gtest-gui.h>
#include "gtest/gtest.h"
#include "gmock/gmock.h"

#pragma comment(lib, "gmock.lib")

class Mytest : public testing::TestWithParam<std::tuple<int,int,int>>
{
};


INSTANTIATE_TEST_CASE_P(MyTestname, Mytest, ::testing::Values(
    std::make_tuple(1, 5, 7),
    std::make_tuple(2, 4, 6),
    std::make_tuple(3, 7, 11)
));

TEST_P(Mytest, Foo)
{
    auto parms = GetParam();
}


TEST(TestCase, Test)
{
	EXPECT_EQ(1 + 1, 2);
}

int main(int argc, char* argv[])
{
	testing::InitGoogleTest(&argc, argv);
	testing::InitGoogleTestGui(&argc, argv);

	return RUN_ALL_TESTS();
}

Boosttestui is picking up public void methods as 'tests'

        public void TestMe1() { }
        public void TestMe2() { }
        public void TestMe3() { }
        public void TestMe4() { }
        public void TestMe5() { }

Boosttestui does not appear at all using remote-desktop

setup:

• two physical monitors, main screen on the left, second screen on the right.
• remote desktop into the machine using a different setup: main screen on the right, second on the left.

the stored x,y coordinates are now 'off screen' and the main window is invisible.

I think its basically this issue:
CobaltFusion/DebugViewPP#72
which you fixed in debugview, but not here yet.

Allow Shift-click to select/deselect a range of tests

If I have a group of tests to enable, it makes sense to click the first test, hold shift and click the last test to select/deselect/toggle the tests.

loading some nunit dlls this message occurs

This is not a duplicate of #1, I checked that the [TextFixture] and [Test] attributes are present.

Strange drawing artifacts?

This happens on Windows 8.1 if you drag/resize the window slowly.

opening a new file while in repeat-test mode is weird

scenario:

• open a test
• set 'repeat' on
• press 'play'

now it is running.

• file->open-> some other test

what happens:

• the log window is cleared
• the testing of the previous test that was still repeating continues

and now I get:

---

Boost Test Runner

Did you forget to #include <gtest/gtest-gui.h>?

OK Help

because that is exactly what I forgot :)

The point here is, it might be clearer to stop the testing before trying to open a new test, because if you open a new test, you probably did not intent to keep running the current test.