id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
13082	Add a way to identify the executable as a boost-test	jan.wilmans@…	Gennadiy Rozental	"I propose to standardise a command-line option to identify the executable as a certain kind of test:
I will propose this to boost.test and google.test as well.
My personal usecase is the identification of tests for 
BoostTestUi (the name is somewhat misleading, it is a test-runner for google-, boost-, catch- and nunit- tests, see github/BoostTestUi.)

Currently this requires re-compilation of the test with a special header, I would like to prevent the need for that.

--test-runner-identification
framework: boost.test
version: x.x

--test-runner-identification
framework: google.test
version: x.x

--test-runner-identification
framework: catch.test
version: x.x

This will allow test-runners to identify the test-framework used to build the test.
That way the test-runners can know what command-line parameters are available to do things like:
- list all the tests
- run specific tests

finally, to let the user attach a debugger to the test this kind of code could added in the main():
(for catch that may already exist, I did not check)

notice that this option can have any name, we need only 1 standardised option --test-runner-identification, because once we know what we're dealing with, we can just use the respective command-line options.


  if (arg == ""--gui-wait"")
  {
      std::cout << ""#waiting"" << std::endl;
      std::getchar();
  }



"	Feature Requests	new	To Be Determined	test	Boost 1.64.0	Problem		test identification test-runner	jan.wilmans@…