<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
	<title type="html"><![CDATA[Gurock Software Support Forum - Feature request: Next button inside Test Run]]></title>
	<link rel="self" href="http://forum.gurock.com/feed/atom/topic/333/"/>
	<updated>2009-12-28T10:07:59Z</updated>
	<generator>PunBB</generator>
	<id>http://forum.gurock.com/topic/333/feature-request-next-button-inside-test-run/</id>
		<entry>
			<title type="html"><![CDATA[Re: Feature request: Next button inside Test Run]]></title>
			<link rel="alternate" href="http://forum.gurock.com/post/1027/#p1027"/>
			<content type="html"><![CDATA[<p>Hello,</p><p>Thanks for the suggestion, this feature is already on our feature request list. The reason we haven&#039;t implemented it yet is that it may be difficult to decide (and probably to understand) what &#039;next&#039; means. Since you can get to a test from multiple locations (from the todos, the run overview or the tests for a case, for example), &#039;next&#039; could mean different things depending on where you are coming from.</p><p>If you are coming from the todo page, &#039;next&#039; would ideally point to the next test in your todo list. If you are coming from the test run overview, people would probably expect that &#039;next&#039; would point to the next test of the run etc. It&#039;s probably difficult to get this feature right, so that &#039;next&#039; always points to the test the user wants to process next.</p><p>However, we will look into this feature after releasing the 1.0.</p><p>Regards,<br />Tobias</p>]]></content>
			<author>
				<name><![CDATA[tgurock]]></name>
				<uri>http://forum.gurock.com/user/4/</uri>
			</author>
			<updated>2009-12-28T10:07:59Z</updated>
			<id>http://forum.gurock.com/post/1027/#p1027</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Feature request: Next button inside Test Run]]></title>
			<link rel="alternate" href="http://forum.gurock.com/post/1026/#p1026"/>
			<content type="html"><![CDATA[<p>Currently it&#039;s possible to add test result or mark as retest for test case inside test run.</p><p>Ability to move to next test case will be useful. It will allow to decrease number of clicks during test run execution by tester.</p>]]></content>
			<author>
				<name><![CDATA[arch]]></name>
				<uri>http://forum.gurock.com/user/40/</uri>
			</author>
			<updated>2009-12-26T09:39:53Z</updated>
			<id>http://forum.gurock.com/post/1026/#p1026</id>
		</entry>
</feed>

