<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Version 2.5: Faster, Better, More Compatible</title>
	<atom:link href="http://blog.utest.com/version-2-5-faster-better-more-compatible/2009/08/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.utest.com/version-2-5-faster-better-more-compatible/2009/08/</link>
	<description>Software Testing Community</description>
	<lastBuildDate>Wed, 08 Feb 2012 08:18:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: uTest Tester</title>
		<link>http://blog.utest.com/version-2-5-faster-better-more-compatible/2009/08/comment-page-1/#comment-14436</link>
		<dc:creator>uTest Tester</dc:creator>
		<pubDate>Fri, 14 Aug 2009 17:02:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.utest.com/?p=1321#comment-14436</guid>
		<description>Nice to have the updates on uTest platform.
Few things that i would like to see are

1. A user should be able to see all the bugs posted by him till date, so that he can learn from his past experiences. Currently he can see bugs on his current projects only. If in case some project has multiple releases then user cannot look back for past bugs posted by him in the same project.

2. Once all the bugs are processed for a project there should be a gap of 2 - 3 days before project is clossed . This will give the bug poster a timeframe to raise disputes if any. Currently if project owner chooses to reject few bugs and close the project then the tester has no method to raise disputes.

3. Since this is a crowd sourced system, there should be some method to see the Top 10 Bug posters in the system on the basis of total bug posted and also on the basis of ratings. And if possible uTest should reward them too for there consistent efforts in the participation.

4. The total bugs count that is shown in user profile block, when some one hoovers over the testers name in the bugs list, it shows only the bugs approved, it doesnot take in account disputed approved. the total should be bugs approved + disputes approved for the count of total bugs approved shown in the user short profile.

5. The bonus system and special payments are not well managed, generally tester has to follow up the project managers for the payments of bonuses and extra rates. This should be more efficient.

6. If a user click save and submit multiple times to submit a bug, it add multiple bugs a strict check should be implemented so that duplicate bugs are not filled in.

7. A weekly newsletter should be generated which indicates what all projects are going to come up in the given week so that testers can schedule there time accordingly.

These have been some of the most important features that I think should get integrated as soon as possible.

Thanks for being supportive and building a strong portal.
Best of luck
uTest Tester :)</description>
		<content:encoded><![CDATA[<p>Nice to have the updates on uTest platform.<br />
Few things that i would like to see are</p>
<p>1. A user should be able to see all the bugs posted by him till date, so that he can learn from his past experiences. Currently he can see bugs on his current projects only. If in case some project has multiple releases then user cannot look back for past bugs posted by him in the same project.</p>
<p>2. Once all the bugs are processed for a project there should be a gap of 2 &#8211; 3 days before project is clossed . This will give the bug poster a timeframe to raise disputes if any. Currently if project owner chooses to reject few bugs and close the project then the tester has no method to raise disputes.</p>
<p>3. Since this is a crowd sourced system, there should be some method to see the Top 10 Bug posters in the system on the basis of total bug posted and also on the basis of ratings. And if possible uTest should reward them too for there consistent efforts in the participation.</p>
<p>4. The total bugs count that is shown in user profile block, when some one hoovers over the testers name in the bugs list, it shows only the bugs approved, it doesnot take in account disputed approved. the total should be bugs approved + disputes approved for the count of total bugs approved shown in the user short profile.</p>
<p>5. The bonus system and special payments are not well managed, generally tester has to follow up the project managers for the payments of bonuses and extra rates. This should be more efficient.</p>
<p>6. If a user click save and submit multiple times to submit a bug, it add multiple bugs a strict check should be implemented so that duplicate bugs are not filled in.</p>
<p>7. A weekly newsletter should be generated which indicates what all projects are going to come up in the given week so that testers can schedule there time accordingly.</p>
<p>These have been some of the most important features that I think should get integrated as soon as possible.</p>
<p>Thanks for being supportive and building a strong portal.<br />
Best of luck<br />
uTest Tester <img src='http://blog.utest.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

