So I won’t forget:
- [WayBack] sglienke / TestInsight / issues / #82 – Not work with active test project — Bitbucket
- When you have a project group that has multiple TestInsight enabled projects, the active one is being used.
- When there is no active TestInsight project in a project group, the topmost one is being used
- Only one TestInsight enabled project is being run at a time
- [WayBack] sglienke / TestInsight / issues / #106 – Run and Show Results From Multiple Test Projects — Bitbucket
- Per #82, you cannot run multiple projects, but you can make a TestInsight enabled project that runs others; #106 as an example C++ program for that.
- [WayBack] sglienke / TestInsight / issues / #86 – Consider to show hierarchical structure of fixtures (with DUnitX) — Bitbucket
- Some tools (for instance the DUnit GUI runner) allow you to show/configure the hierarchy of test suites.
- TestInsight only shows the tab Test Fixture (alias for test class) grouped by test classname.
- The aim of TestInsight is to test a few tests so they run fast. Your CI should run longer TestSuite configurations.
- TestInsight has no aim to include TestSuite levels to the output;
- TestExplorer in Visual Studio also does not show the hierarchy (see picture below), but it allows for grouping on various columns.
- [WayBack] sglienke / TestInsight / issues / #108 – Place the “Group by” tab at the top — Bitbucket
Note to self:
The Wiert Corner - irregular stream of stuff 