В Украине, а также в остальных странах СНГ кроме России, нету возможности снимать деньги с paypal, как вы выводите заработаные деньги с Utest.
а дальше стало плохо. проектов мало, все уже не первая итерация, продираться сквозь длинные листы известных багов тоскливо, можно потратить несколько часов и так ничего и не найти. в итоге за пару недель бронза моя протухла.
Я указал профиле что нахожусь в Канаде, до этого указывал что в Америке, читайте мой пост выше.. Заработал 40 долларов и Пейпал поставил как платежный метод. Деньги не пришли. Попросил их перекинуть на Пейонир, сказали перекинут, но сначала прислали вот такое чудное письмо:
I noticed that your profile states that you are located in Canada.
However, your IP history indicates that you are actually in the Ukraine.
When you signed up with uTest you agreed to follow the uTester Code of
Conduct which clearly states to never falsify information in your tester
profile. As such, we have implemented a three strike system. Strike 1 is a
warning, Strike 2 is a temporary account suspension, and Strike 3 is
permanent suspension. This email is to inform you that the stated
infraction is strike 1 and will be recorded on your file. For more
information on our three strike policy you can view our help topic here:
Three Strike Policy | uTest Help.
We Trust But We Test!
Интересное сообщение от одного моего студента по теме - UTest related
I encourage everyone to do as Mikhail says, and join uTest! It's a great way to gain real world testing experience and earn a bit of money along the way.
I had never heard of uTest until Mikhail mentioned it to me; I only joined in March 2012 and began as a "Rated" tester (like everyone). It took me about 3 test cycles to learn the ropes and figure out what was going on, and I had quite a few rejected bugs as a result. Still, I made $40.00 my first month. Once I started to catch on, however, by learning more about how uTest and bug submissions worked, my performance improved significantly!
In month 2, I earned $83.00. Most importantly, I started realizing the importance of finding "Exceptionally Valuable" and "Very Valuable" bugs. Not only are payouts higher but your tester rating increases faster than finding just any bug.
Now in Month 3, I've made $149.00, not counting bugs that have been "Approved" but are still pending payment for the current test cycle. Once the cycle closes, I expect to earn closer to $200. Not only that but, to my surprise, I was just designated a "Favorite" tester by one customer, because 6 of the 7 bugs I found in one cycle were classified as "Very Valuable". As a word of encouragement, my 6 "Very Valuable" bugs were more than any other tester for a particular test cycle - and all the other testers were rated higher than me at "Gold," "Silver" and "Bronze". When tester ratings update tomorrow (Friday), I'm hoping mine climbs to at least "Proven". (BTW - payout amounts per bug increase beginning at the "Bronze" level).
After joining uTest, the 2 biggest tips I can pass along are: 1) make sure you DO NOT SUBMIT DUPLICATE BUGS, and; 2) make sure you STAY WITHIN SCOPE.
These were my 2 biggest mistakes when I started, and my rating suffered as a result. I now constantly refer to both the "Known Bugs" list and the "Scope and Instructions" for all test cycles. Also, whenever possible, I focus my efforts on finding what I think the customer would consider to be "Very Valuable" bugs (at a minimum), over finding just any bug.
alexsplayer (23.02.2014), Bigfoot (13.05.2014), Cara (01.07.2015), DmitryNaymushin (25.11.2015), Julles (04.06.2012), Karged (11.09.2015), ManiKarnika (30.04.2013), MatildaJ (02.01.2013), Noop (01.10.2012), owl (15.10.2013), Siberia_USA (03.04.2016), SleepyMe (13.10.2013), VladK (18.09.2016), Мялка (11.02.2016), Юрий НСК (22.07.2013)
Еще у них на форуме можно проекты найти:http://forums.utest.com/ там каждый день Upcoming Opportunities повляются. Я так пару-тройку проектов нашел.
Последний раз редактировалось belevich; 03.06.2012 в 21:39.
Судя по количеству просмотров тем на ютестовском форуме, читает его небольшой процент тестеров.
Я тоже бываю от случая к случаю, надо бы чаще.
Вот тут по поводу стран, имен, ников и экаунтов. Напечатано еще в 2009 году
Тут тема Software Testing Forums • Login
The list of uTest Best Practices and uTest Worst Practices:
Those best practices are:
1. Be clear (write clearly and concisely)
2. Be professional (read the release details and communicate professionally)
3. Be precise (provide detailed description; accurately categorize your bug types and severity)
4. Be fair (don't overuse the dispute feature, don't submit bugs/surveys multiple times)
5. Be successful (it's quality that matters, not quantity!)
The rewards of following these best practices are obvious (more work, more approved bugs, more money)
Those worst practices are:
1. Poorly written bug reports (unclear descriptions, no screenshots, poor spelling, grammar & punctuation)
2. Lack of preparation (submitting out-of-scope bugs, not reading release description)
3. Bug inflation (overstating bug severity or type)
4. Creating multiple accounts (having more than one uTest account, submitting bugs/surveys/test scripts multiple times)
5. Fake Names ("Software Guy", "Testing Guru", "Joe Cool")
We implemented these rules to raise the level of quality and consistency in the community... to protect the good name of uTest and our uTesters. We're not doing this to pick on anyone, but rather to make sure that all testers are on a level playing field and that no testers are harming the uTest name or the good work of so many testers. As a result of these efforts, the overall quality of the community is improving quickly. If any of these worst practices applies to you, we want you to address them immediately so we don't have to.
In this spirit of community-building, here is an update on the early results of our enforcement of these rules. In the past month, we have addressed the following issues:
* Out-of-scope bugs: 23 testers have exceeded the limits of out-of-scope bugs on one or more releases. We have sent out warning letters to all 23 testers and seen a dramatic reduction in this behavior. For the 3 testers who continued to report multiple out-of-scope bugs, we have permanently removed them from the uTest community. We will continue to watch this closely and will take aggressive action to stop it.
* Testers with multiple uTest accounts: Thus far, we have discovered 21 testers who had multiple accounts (some even had 3 or 4). In many cases, testers volunteered this information to us and we let them choose which account they wanted to keep and deactivated the others. In other cases, testers have tried to lie to us, so we would analyze the evidence (IP addresses, bug samples, writing samples, login days/times, etc). We would then present the evidence to them and then deactivate ALL of their accounts. Important note: if you have multiple uTest accounts, please email email@example.com before Friday, July 31 and tell us which account you would like to keep and which account(s) you would like to deactivate. After that date, if we discover any tester has multiple accounts, we will deactivate all of their accounts permanently.
* Testers who change their country: Some customers need testers from a specific country or countries (examples: US only / Western Europe only / India and Vietnam only). They do this because they want testers who match their customers' locations and we respect their wishes. But some testers have edited their profiles to reflect a country that they don't live in. We've already discovered 45 testers who did this so we changed their country in our database and sent them a warning email. 11 of them re-changed the country in their profile so we have deactivated their accounts permanently. We will continue to monitor this closely to make sure that testers are being honest in their profile. If anyone has a country in their profile that is not accurate, please correct it immediately. We are watching this closely and this offense will get testers removed from the community permanently beginning on Friday, July 31.
* Fake names: Customers don't trust testers who use fake names (example: Joe Cool, Tester Guru, Bug Killer). This causes them to reject bugs from these testers and makes them question their trust for all uTesters. In the past month, we've identified more than 50 active testers who used fake names in their uTest account. We emailed these testers and more than 40 of them promptly corrected their name. For the 14 who did not, we deactivated their accounts permanently. If anyone is using a fake name, please understand that it hurts your credibility with customers and damages the uTest community as a whole. If this applies to you, please address it yourself so we don't have to.
* Excessive disputing of rejected bugs: In researching this, we discovered that 4 testers were disputing rejected bugs at a higher-than-average rate and that too many of these disputes were being declined. We've addressed this with these testers and they have dramatically lowered the % of rejected bugs that they dispute. We will continue to watch this metric closely... it's not a bad thing to dispute a bug, but when a tester is disputing a higher % of bugs than other testers, we will address it with them. If the tester continues to dispute bugs at such a high rate (particularly when the customer and project manager determine that the bug rejection is valid), we will take disciplinary action.
Again, I want to reiterate why we're cracking down: it is not to pick on testers... we're doing it to protect the thousands of testers who are doing good, honest work for our customers. We do it to make certain that you're all on a level playing field and to protect the integrity of the uTest community. In addition to policing yourself, I want to ask for your help -- if you see something suspicious (fake names, multiple identities, inaccurate countries, etc), please point it out to us at firstname.lastname@example.org.
Эту тему просматривают: 4 (пользователей: 0 , гостей: 4)