Training Basics - Revision history

Marku at 21:37, 6 July 2015

2015-07-06T21:37:35Z

Marku at 16:16, 27 November 2014

2014-11-27T16:16:19Z

← Older revision		Revision as of 16:16, 27 November 2014
Line 5:		Line 5:

	The routines are contained in ''software_under_test.c \| h''. The suggested things to '''Try''' will be focused on applying testing techniques on ''sut_mult()''.		The routines are contained in ''software_under_test.c \| h''. The suggested things to '''Try''' will be focused on applying testing techniques on ''sut_mult()''.

			Example option file ''my.opt'' used below for running

			--database "%STRIDE_DIR%\SDK\Windows\out\TestApp.sidb"
			--device TCP:localhost:8000

	== Test Macros ==		== Test Macros ==

Ivailop: /* File IO */

2014-11-27T00:52:57Z

File IO

← Older revision		Revision as of 00:52, 27 November 2014
Line 64:		Line 64:

	* [[File_Transfer_Services \| File IO Services]]		* [[File_Transfer_Services \| File IO Services]]
	* [[Passing ~~INI-formatted~~ input]] to ~~a Test Suite~~		* [[Parameterized Test Units \| Passing parameter input]] to a Test Suite
	* [[Runtime_Test_Services#srTestGetParam \| Reading INI-formatted input]] from a Test Suite

	The Test Suite is called '''TestFileIO''' and is implemented in two source files: '''testfileio.cpp''' and '''testfileio.h'''. The comments and descriptions are contained in the header file. One test case (method) is already implemented and one test method that can be used to make changes to is called '''TryStuff'''. Currently the ''TryStuff'' test method is set to ''not in use''.		The Test Suite is called '''TestFileIO''' and is implemented in two source files: '''testfileio.cpp''' and '''testfileio.h'''. The comments and descriptions are contained in the header file. One test case (method) is already implemented and one test method that can be used to make changes to is called '''TryStuff'''. Currently the ''TryStuff'' test method is set to ''not in use''.

Ivailop: /* Parameters */

2014-11-27T00:52:23Z

Parameters

← Older revision		Revision as of 00:52, 27 November 2014
Line 38:		Line 38:
	The following articles are related to this example:		The following articles are related to this example:

	* [[Parameterized Test Units \| Passing ~~arguments]] to a Test Suite constructor~~		* [[Parameterized Test Units \| Passing parameter input]] to a Test Suite
	* [[Passing INI-formatted input]] to a Test Suite		* [[Runtime_Test_Services#srTestGetParam \| Reading parameters]] from a Test Suite
	* [[Runtime_Test_Services#srTestGetParam \| Reading ~~INI-formatted input~~]] from a Test Suite

	The Test Suite is called '''TestParameters''' and is implemented in two source files: '''testparameters.cpp''' and '''testparameters.h'''. The comments and descriptions are contained in the header file. Two test cases are already implemented and one test method that can be used to make changes to is called '''TryStuff'''. Currently the ''TryStuff'' test method is set to ''not in use''.		The Test Suite is called '''TestParameters''' and is implemented in two source files: '''testparameters.cpp''' and '''testparameters.h'''. The comments and descriptions are contained in the header file. Two test cases are already implemented and one test method that can be used to make changes to is called '''TryStuff'''. Currently the ''TryStuff'' test method is set to ''not in use''.
Line 57:		Line 56:
	* Add test code for ''sut_mult()'' using arguments from the command line		* Add test code for ''sut_mult()'' using arguments from the command line
	* Add test code for ''sut_mult()'' using your own created ini file		* Add test code for ''sut_mult()'' using your own created ini file
	* Change the content of ini file .. re-run the test suite		* Change the content of the ini file .. re-run the test suite

	== File IO ==		== File IO ==

Ivailop: /* File IO */

2014-11-26T23:21:34Z

File IO

← Older revision		Revision as of 23:21, 26 November 2014
Line 90:		Line 90:
	stride --options_file my.opt --run "TestFileIO(%STRIDE_DIR%/samples/testfileio.ini)"		stride --options_file my.opt --run "TestFileIO(%STRIDE_DIR%/samples/testfileio.ini)"

	You can take a look at the results in '''~~TestApp~~.~~xml~~'''.		You can take a look at the results by opening the generated '''stride.html''' in your browser.

	Consider the following for '''TryStuff:'''		Consider the following for '''TryStuff:'''
	* Add a test for ''sut_mult()'' using a different input file		* Add test code for ''sut_mult()'' using a different input file
	* Update the ''testfileio.ini'' file to include a second file for input		* Update the ''testfileio.ini'' file to include a second file for input

Ivailop: /* Parameters */

2014-11-26T23:19:16Z

Parameters

← Older revision		Revision as of 23:19, 26 November 2014
Line 48:		Line 48:
	stride --options_file my.opt --run "TestParameters(10,10)"		stride --options_file my.opt --run "TestParameters(10,10)"

	You can take a look at the results in '''~~TestApp~~.~~xml~~'''.		You can take a look at the results by opening the generated '''stride.html''' in your browser.

	Now run a second time and use a file with INI-formatted input:		Now run a second time and use a file with INI-formatted input:
Line 55:		Line 55:

	Consider the following for '''TryStuff:'''		Consider the following for '''TryStuff:'''
	* Add a test for ''sut_mult()'' using arguments from the command line		* Add test code for ''sut_mult()'' using arguments from the command line
	* Add a test for ''sut_mult()'' using your own created ini file		* Add test code for ''sut_mult()'' using your own created ini file
	* Change the content of ini file .. re-run the test suite		* Change the content of ini file .. re-run the test suite

Ivailop: /* Test Macros */

2014-11-26T23:18:30Z

Test Macros

← Older revision		Revision as of 23:18, 26 November 2014
Line 26:		Line 26:

	Consider the following for '''TryStuff''':		Consider the following for '''TryStuff''':
	* Add a test code for the ''sut_mult()'' routine (remember to remove the ''set status'' call)		* Add test code for the ''sut_mult()'' routine (remember to remove the ''set status'' call)
	* Add an ''Assert'' macro (verses an ''Expect''). Do you understand the difference?		* Add an ''Assert'' macro (verses an ''Expect''). Do you understand the difference?
	* Throw in a ''Note'' macro .. provides more viability to the test logic		* Throw in a ''Note'' macro .. provides more viability to the test logic

Ivailop: /* Test Macros */

2014-11-26T23:16:34Z

Test Macros

← Older revision		Revision as of 23:16, 26 November 2014
Line 29:		Line 29:
	* Add an ''Assert'' macro (verses an ''Expect''). Do you understand the difference?		* Add an ''Assert'' macro (verses an ''Expect''). Do you understand the difference?
	* Throw in a ''Note'' macro .. provides more viability to the test logic		* Throw in a ''Note'' macro .. provides more viability to the test logic
	* Change the test method documentation (in testmacros.h) and see how it shows up automatically in the test report		* Change the test method documentation (in ''testmacros.h'') and see how it shows up automatically in the test report
	* Change the test method name		* Change the test method name

Ivailop: /* Test Macros */

2014-11-26T23:15:58Z

Test Macros

← Older revision		Revision as of 23:15, 26 November 2014
Line 23:		Line 23:
	stride --options_file my.opt --run "TestMacros"		stride --options_file my.opt --run "TestMacros"

	You can take a look at the results in '''~~TestApp~~.~~xml~~'''.		You can take a look at the results by opening the generated '''stride.html''' in your browser.

	Consider the following for '''TryStuff''':		Consider the following for '''TryStuff''':
	* Add a test for the ''sut_mult()'' routine (remember to remove the ''set status'' ~~routine~~)		* Add a test code for the ''sut_mult()'' routine (remember to remove the ''set status'' call)
	* Add an ''Assert'' macro (verses an ''Expect''). Do you understand the difference?		* Add an ''Assert'' macro (verses an ''Expect''). Do you understand the difference?
	* Throw in a ''Note'' macro .. provides more viability to the test logic		* Throw in a ''Note'' macro .. provides more viability to the test logic
	* Change the ~~''TryStuff''~~ method ~~declaration comment~~ (testmacros.h) and see how it shows up automatically in the test report		* Change the test method documentation (in testmacros.h) and see how it shows up automatically in the test report
	* Change the ~~''TryStuff''~~ method name		* Change the test method name

	== Parameters ==		== Parameters ==

Ivailop: /* Test Macros */

2014-11-26T22:52:55Z

Test Macros

← Older revision		Revision as of 22:52, 26 November 2014
Line 8:		Line 8:
	== Test Macros ==		== Test Macros ==

	This test suite focuses on leveraging ~~assertion~~ macros when writing test cases. Note that it is '''not''' required to use test macros. A test case (method) can simply return a value to indicate ''pass'' or ''fail'' - refer to [[Indicating_Pass/Fail_in_a_Test_Method \| this]] article for details.		This test suite focuses on leveraging test macros when writing test cases. Note that it is '''not''' required to use test macros. A test case (method) can simply return a value to indicate ''pass'' or ''fail'' - refer to [[Indicating_Pass/Fail_in_a_Test_Method \| this]] article for details.

	The following articles are related to this example:		The following articles are related to this example:

← Older revision		Revision as of 21:37, 6 July 2015
Line 13:		Line 13:
	== Test Macros ==		== Test Macros ==

	This ~~test suite~~ focuses on leveraging test macros when writing test cases. Note that it is '''not''' required to use test macros. A test case (method) can simply return a value to indicate ''pass'' or ''fail'' ~~- refer to [[Indicating_Pass/Fail_in_a_Test_Method \| this]] article for details~~.		This Test Unit sample focuses on leveraging test macros when writing test cases. Note that it is '''not''' required to use test macros. A test case (method) can simply return a value to indicate ''pass'' or ''fail''.

	The following articles are related to this example:		The following articles are related to this example:
	* [[~~Test_Units \|~~ Test ~~Suite~~]] packaging options		* [[Test Unit]] packaging options
	* Available [[~~Test_Macros \|~~ Test Macros]]		* Available [[Test Macros]]
	* [[~~Test_Macros#Notes \|~~ Notes]] ~~and [[Test_Log \| Test Logs]]~~		* Adding [[Notes]] to the test logic
	* Creating [[Test_Documentation_in_C/C%2B%2B \| Doxygen style]] descriptions within header files		* Creating [[Test_Documentation_in_C/C%2B%2B \| Doxygen style]] descriptions within test header files
	* ~~Executing Test Suites using the~~ [[~~STRIDE_Runner \| Runner~~]]		* How [[Running Tests]] works

	The Test ~~Suite~~ is called '''TestMacros''' and is implemented in two source files: '''testmacros.cpp''' and '''testmacros.h'''. The comments and descriptions are contained in the header file. One test case (method) is already implemented and one test method that can be used to make changes to is called '''TryStuff'''. Currently the ''TryStuff'' test method is set to ''not in use''.		The Test Unit is called '''TestMacros''' and is implemented in two source files: '''testmacros.cpp''' and '''testmacros.h'''. The comments and descriptions are contained in the header file. One test case (method) is already implemented and one test method that can be used to make changes to is called '''TryStuff'''. Currently the ''TryStuff'' test method is set to ''not in use''.

	First thing to do is run the ''TestMacros'' ~~Suite~~. Start the '''TestApp.exe''' and use the following command:		First thing to do is run the ''TestMacros'' Test Unit. Start the '''TestApp.exe''' and use the following command:

	stride --options_file my.opt --run "TestMacros"		stride --options_file my.opt --run "TestMacros"
Line 39:		Line 39:
	== Parameters ==		== Parameters ==

	This ~~test suite~~ focuses on using parameters when writing test cases. Note that this sample has been implemented to (i) ensure parameters have been passed and (ii) support two different techniques for passing in parameters.		This Test Unit sample focuses on using parameters when writing test cases. Note that this sample has been implemented to (i) ensure parameters have been passed and (ii) support two different techniques for passing in parameters.

	The following articles are related to this example:		The following articles are related to this example:

	* [[Parameterized Test Units \| Passing parameter input]] to a Test ~~Suite~~		* [[Parameterized Test Units \| Passing parameter input]] to a Test Unit
	* [[Runtime_Test_Services#srTestGetParam \| Reading parameters]] from a Test ~~Suite~~		* [[Runtime_Test_Services#srTestGetParam \| Reading parameters]] from a Test Unit

	The Test ~~Suite~~ is called '''TestParameters''' and is implemented in two source files: '''testparameters.cpp''' and '''testparameters.h'''. The comments and descriptions are contained in the header file. Two test cases are already implemented and one test method that can be used to make changes to is called '''TryStuff'''. Currently the ''TryStuff'' test method is set to ''not in use''.		The Test Unit is called '''TestParameters''' and is implemented in two source files: '''testparameters.cpp''' and '''testparameters.h'''. The comments and descriptions are contained in the header file. Two test cases are already implemented and one test method that can be used to make changes to is called '''TryStuff'''. Currently the ''TryStuff'' test method is set to ''not in use''.

	First thing to do is run the ''TestParameters'' ~~Suite~~. Start the '''TestApp.exe''' and use the following command:		First thing to do is run the ''TestParameters'' Test Unit. Start the '''TestApp.exe''' and use the following command:

	stride --options_file my.opt --run "TestParameters(10,10)"		stride --options_file my.opt --run "TestParameters(10,10)"
Line 61:		Line 61:
	* Add test code for ''sut_mult()'' using arguments from the command line		* Add test code for ''sut_mult()'' using arguments from the command line
	* Add test code for ''sut_mult()'' using your own created ini file		* Add test code for ''sut_mult()'' using your own created ini file
	* Change the content of the ini file .. re-run the ~~test suite~~		* Change the content of the ini file .. re-run the Test Unit

	== File IO ==		== File IO ==
	This ~~test suite~~ focuses on reading content from a host file to be used by the executing test logic. Note that this sample uses the [[Runtime_Test_Services#C.2B.2B_Test_Classes \| srTest]] base class.		This Test Unit sample focuses on reading content from a host file to be used by the executing test logic. Note that this sample uses the [[Runtime_Test_Services#C.2B.2B_Test_Classes \| srTest]] base class.

	The following articles are related to this example:		The following articles are related to this example:

	* [[File_Transfer_Services \| File IO Services]]		* [[File_Transfer_Services \| File IO Services]]
	* [[Parameterized Test Units \| Passing parameter input]] to a Test ~~Suite~~		* [[Parameterized Test Units \| Passing parameter input]] to a Test Unit

	The Test ~~Suite~~ is called '''TestFileIO''' and is implemented in two source files: '''testfileio.cpp''' and '''testfileio.h'''. The comments and descriptions are contained in the header file. One test case (method) is already implemented and one test method that can be used to make changes to is called '''TryStuff'''. Currently the ''TryStuff'' test method is set to ''not in use''.		The Test Unit is called '''TestFileIO''' and is implemented in two source files: '''testfileio.cpp''' and '''testfileio.h'''. The comments and descriptions are contained in the header file. One test case (method) is already implemented and one test method that can be used to make changes to is called '''TryStuff'''. Currently the ''TryStuff'' test method is set to ''not in use''.

	The Test ~~Suite~~ is using an INI file (''stride/samples/testfileio.ini'') to indicate what input file content to use:		The Test Unit is using an INI file (''stride/samples/testfileio.ini'') to indicate what input file content to use:

	## Required parameters used for testing file IO		## Required parameters used for testing file IO
Line 89:		Line 89:
	53,27,80		53,27,80

	First thing to do is run the ''TestFileIO'' ~~Suite~~. Start the '''TestApp.exe''' and use the following command:		First thing to do is run the ''TestFileIO'' Test Unit. Start the '''TestApp.exe''' and use the following command:

	stride --options_file my.opt --run "TestFileIO(%STRIDE_DIR%/samples/testfileio.ini)"		stride --options_file my.opt --run "TestFileIO(%STRIDE_DIR%/samples/testfileio.ini)"