STRIDE Test Space - Revision history

Marku: /* Uploading Results */

2012-06-01T23:18:03Z

Uploading Results

← Older revision		Revision as of 23:18, 1 June 2012
Line 16:		Line 16:
	===Uploading Results===		===Uploading Results===

	New results set can be easily uploaded using the automatic upload feature in the [[Running_Test_Units#Publishing_Results_to_STRIDE_Test_Space\|STRIDE Runner]]. You can also upload XML results data files manually using the web interface by navigating to the detail view for a specific test case and clicking the ''upload data'' button.		New results set can be easily uploaded using the automatic upload feature in the [[Running_Test_Units#Publishing_Results_to_STRIDE_Test_Space\|STRIDE Runner]]. You can also upload XML results data files manually using the web interface by navigating to the detail view for a specific test case and clicking the ''upload data'' button. For information on the XML Schema refer [[Test_Space_XML_Schema \| here]].

	===Viewing Results===		===Viewing Results===

Marku at 22:03, 9 June 2011

2011-06-09T22:03:55Z

← Older revision		Revision as of 22:03, 9 June 2011
Line 1:		Line 1:
	== What is STRIDE Test Space? ==		== What is STRIDE Test Space? ==

	STRIDE Test Space is a hosted web application for storing and analyzing your test results. Test Space accepts data that results from the execution of STRIDE Test Units or Test Scripts. Data is uploaded to Test Space manually (using the web interface) or automatically from ~~one of~~ the ~~STRIDE execution tools (~~[[~~Stride Runner\|~~STRIDE Runner]] ~~or [[STRIDE Studio]])~~. Once data is uploaded, it is retained until it is manually removed or automatically deleted (depending on the space configuration).		STRIDE Test Space is a hosted web application for storing and analyzing your test results. Test Space accepts data that results from the execution of STRIDE Test Units or Test Scripts. Data is uploaded to Test Space manually (using the web interface) or automatically from the [[STRIDE Runner]]. Once data is uploaded, it is retained until it is manually removed or automatically deleted (depending on the space configuration).

	STRIDE Test Space organizes results in a hierarchy of ''projects'', ''test spaces'' and ''result sets''. Each time you upload data to a test space, a new result set is created (unless you explicitly add your data to an existing one). With a given result set, test results are further organized into test suites containing test cases. Any number of these organizational entities can be used to create a fluid hierarchy of test results that adapts to shifting needs during a product lifecycle.		STRIDE Test Space organizes results in a hierarchy of ''projects'', ''test spaces'' and ''result sets''. Each time you upload data to a test space, a new result set is created (unless you explicitly add your data to an existing one). With a given result set, test results are further organized into test suites containing test cases. Any number of these organizational entities can be used to create a fluid hierarchy of test results that adapts to shifting needs during a product lifecycle.
Line 16:		Line 16:
	===Uploading Results===		===Uploading Results===

	New results set can be easily uploaded using the automatic upload ~~features~~ in the [[Running_Test_Units#Publishing_Results_to_STRIDE_Test_Space\|STRIDE Runner~~]] or [[STRIDE Studio~~]]. You can also upload XML results data files manually using the web interface by navigating to the detail view for a specific test case and clicking the ''upload data'' button.		New results set can be easily uploaded using the automatic upload feature in the [[Running_Test_Units#Publishing_Results_to_STRIDE_Test_Space\|STRIDE Runner]]. You can also upload XML results data files manually using the web interface by navigating to the detail view for a specific test case and clicking the ''upload data'' button.

	===Viewing Results===		===Viewing Results===

Marku: /* Messages */

2010-06-04T18:26:25Z

Messages

← Older revision		Revision as of 18:26, 4 June 2010
Line 116:		Line 116:

	[[Category: Test Space]]		[[Category: Test Space]]
	~~[[Category:STRIDE Test Space]]~~

Mikee: /* Test Case */

2010-02-19T23:25:14Z

Test Case

← Older revision		Revision as of 23:25, 19 February 2010
Line 84:		Line 84:
	===Test Case===		===Test Case===

	This is the unit of measure for test results - ~~and~~ single pass/fail entity. Test cases can be supplemented with additional information in the form of annotations and comments.		This is the unit of measure for test results - a single pass/fail entity. Test cases can be supplemented with additional information in the form of annotations and comments.

	===Test Suite===		===Test Suite===

Ivailop: /* Annotation */

2010-02-13T07:08:26Z

Annotation

← Older revision		Revision as of 07:08, 13 February 2010
Line 92:		Line 92:
	===Annotation===		===Annotation===

	Annotations provide additional information about test cases or test suites. Each annotation has a level associated with it as well as a name and description. For this reason, the STRIDE Test Framework maps ~~log~~ messages from ~~srLOG macros~~ to annotations.		Annotations provide additional information about test cases or test suites. Each annotation has a level associated with it as well as a name and description. For this reason, the STRIDE Test Framework maps assert/note messages from [[Test Code Macros]] to annotations.

	===Result Set===		===Result Set===

Marku: /* Messages */

2009-09-19T00:04:15Z

Messages

← Older revision		Revision as of 00:04, 19 September 2009
Line 78:		Line 78:
	===Messages===		===Messages===

	Messages are light-weight discussion threads with context - they can apply to a specific suite, result set or to generally to a test space. In the latter case, users can select a title for the message thread since there can be more than one message thread for a given test space. Messages (and comments thereto) support limited formatting via [http://hobix.com/textile/ Textile markdown]. Messages can be added to result sets and suites by selecting the [[Image:Comments-empty.JPG]] icon. If a message already exists for a particular item, the icon will appear with a black background.		Messages are light-weight discussion threads with context - they can apply to a specific suite, result set or to generally to a test space. In the latter case, users can select a title for the message thread since there can be more than one message thread for a given test space. Messages (and comments thereto) support limited formatting via [http://redcloth.org/hobix.com/textile/ Textile markdown]. Messages can be added to result sets and suites by selecting the [[Image:Comments-empty.JPG]] icon. If a message already exists for a particular item, the icon will appear with a black background.

	==Glossary of Terms==		==Glossary of Terms==

Mikee at 22:22, 9 September 2009

2009-09-09T22:22:01Z

← Older revision		Revision as of 22:22, 9 September 2009
Line 30:		Line 30:
	This view is the default view for Test Space. This data is also available as an RSS feed (your browser should detect the feed and allow you to subscribe).		This view is the default view for Test Space. This data is also available as an RSS feed (your browser should detect the feed and allow you to subscribe).

	[[Image:Test_space_overview.png]]		[[Image:Test_space_overview.png\|600px]]

	====All Projects====		====All Projects====
Line 36:		Line 36:
	The ''All Projects'' view shows all test spaces to which you have access, grouped by project. This is typically how users will navigate to specific test spaces, although links from events will also take you to specific test spaces. This view shows the space names, result set counts, and two spark-line graphs of the pass and fail count trends. For stable test-beds, these graphs should appear flat - otherwise they will indicate the trend of pass and fail counts for your current development effort.		The ''All Projects'' view shows all test spaces to which you have access, grouped by project. This is typically how users will navigate to specific test spaces, although links from events will also take you to specific test spaces. This view shows the space names, result set counts, and two spark-line graphs of the pass and fail count trends. For stable test-beds, these graphs should appear flat - otherwise they will indicate the trend of pass and fail counts for your current development effort.

	[[Image:Test_space_projects.png]]		[[Image:Test_space_projects.png\|600px]]

	====Project View====		====Project View====
Line 48:		Line 48:
	The last segment is the result set list. This shows all result sets in descending sequence order (most recently added result sets at top). Each row in this tabular view includes the result set name and description, total duration, pass and fail totals and any baseline comparison results (if comparisons are activated for the space).		The last segment is the result set list. This shows all result sets in descending sequence order (most recently added result sets at top). Each row in this tabular view includes the result set name and description, total duration, pass and fail totals and any baseline comparison results (if comparisons are activated for the space).

	[[Image:Test_space_space.png]]		[[Image:Test_space_space.png\|600px]]

	====Results View====		====Results View====
Line 56:		Line 56:
	Each row in the display also shows the pass/fail status for test cases, or the total number of each for test suites. Baseline data comparison data is shown to the right, if a comparison is set-up in the test space's properties. Baseline fields will generally only be displayed when there are differences with the baseline data - these differences can include status and duration (if timing data is present in the baseline).		Each row in the display also shows the pass/fail status for test cases, or the total number of each for test suites. Baseline data comparison data is shown to the right, if a comparison is set-up in the test space's properties. Baseline fields will generally only be displayed when there are differences with the baseline data - these differences can include status and duration (if timing data is present in the baseline).

	[[Image:Test_space_results.png]]		[[Image:Test_space_results.png\|600px]]

	===Baseline Comparison===		===Baseline Comparison===

Mikee at 22:03, 9 September 2009

2009-09-09T22:03:15Z

← Older revision		Revision as of 22:03, 9 September 2009
Line 36:		Line 36:
	The ''All Projects'' view shows all test spaces to which you have access, grouped by project. This is typically how users will navigate to specific test spaces, although links from events will also take you to specific test spaces. This view shows the space names, result set counts, and two spark-line graphs of the pass and fail count trends. For stable test-beds, these graphs should appear flat - otherwise they will indicate the trend of pass and fail counts for your current development effort.		The ''All Projects'' view shows all test spaces to which you have access, grouped by project. This is typically how users will navigate to specific test spaces, although links from events will also take you to specific test spaces. This view shows the space names, result set counts, and two spark-line graphs of the pass and fail count trends. For stable test-beds, these graphs should appear flat - otherwise they will indicate the trend of pass and fail counts for your current development effort.

	[[Image:~~test_space_projects~~.~~JPG~~]]		[[Image:Test_space_projects.png]]

	====Project View====		====Project View====
Line 48:		Line 48:
	The last segment is the result set list. This shows all result sets in descending sequence order (most recently added result sets at top). Each row in this tabular view includes the result set name and description, total duration, pass and fail totals and any baseline comparison results (if comparisons are activated for the space).		The last segment is the result set list. This shows all result sets in descending sequence order (most recently added result sets at top). Each row in this tabular view includes the result set name and description, total duration, pass and fail totals and any baseline comparison results (if comparisons are activated for the space).

	[[Image:~~test_space_space~~.~~JPG~~]]		[[Image:Test_space_space.png]]

	====Results View====		====Results View====
Line 56:		Line 56:
	Each row in the display also shows the pass/fail status for test cases, or the total number of each for test suites. Baseline data comparison data is shown to the right, if a comparison is set-up in the test space's properties. Baseline fields will generally only be displayed when there are differences with the baseline data - these differences can include status and duration (if timing data is present in the baseline).		Each row in the display also shows the pass/fail status for test cases, or the total number of each for test suites. Baseline data comparison data is shown to the right, if a comparison is set-up in the test space's properties. Baseline fields will generally only be displayed when there are differences with the baseline data - these differences can include status and duration (if timing data is present in the baseline).

	[[Image:~~test_space_results~~.~~JPG~~]]		[[Image:Test_space_results.png]]

	===Baseline Comparison===		===Baseline Comparison===

Mikee: /* Overview */

2009-09-09T22:01:40Z

Overview

← Older revision		Revision as of 22:01, 9 September 2009
Line 30:		Line 30:
	This view is the default view for Test Space. This data is also available as an RSS feed (your browser should detect the feed and allow you to subscribe).		This view is the default view for Test Space. This data is also available as an RSS feed (your browser should detect the feed and allow you to subscribe).

	[[Image:~~test_space_overview~~.~~PNG~~]]		[[Image:Test_space_overview.png]]

	====All Projects====		====All Projects====

Mikee: /* Overview */

2009-09-09T22:00:39Z

Overview

← Older revision		Revision as of 22:00, 9 September 2009
Line 30:		Line 30:
	This view is the default view for Test Space. This data is also available as an RSS feed (your browser should detect the feed and allow you to subscribe).		This view is the default view for Test Space. This data is also available as an RSS feed (your browser should detect the feed and allow you to subscribe).

	[[Image:test_space_overview.~~JPG~~]]		[[Image:test_space_overview.PNG]]

	====All Projects====		====All Projects====