Feedback on UTS

I spoke with Jimmy yesterday and encounterd most of the same issues.

1) If there is only 1 option to choose, don display it at all.
2)I encountered the same seems that the session has trouble with users.
3)We have to rigorously work on some workflow issues, after this we should focus on removing and editing most of the interface text.
4)I encountered the same problem, boombatower should already be working on this.

1. Fixed. - Field disabled on study creation.
2. Is that we you are trying to participate in study? If so that is in new test environment which I need to add a feature to allow you to create a test environment to be used as the base environment instead of a fresh drupal install.
3. Will look into.
4. Will look into.

Fixed all the exceptions/warnings generated when ending testing session, or deleting study that are for some reason hidden and only show up in apache error log.

OK, So I have my say, too...

I created a new Study, and also a task for this. What was quite confusing is the "record steps" for the task. I did this before I saved the task - should not have to. I recorded the steps but was not taken back to the task in the end. And I think I also lost the task because it was not saved. Miraculously when I wanted to create a new task, the recorded steps were there for the new one.

Set the task to "active". Now I could participate. But now I had to log in: strange, but my admin username and password did not work. So I had to leave it unfinished.

In the end, I wanted to analyze my results, but there appeared to be nothing to be analyzed (understandably, maybe). Repeatedly pressing the analyze tab did not get me anywhere.

Well, in order to only bring bugs and errors in: I thing I understood the general concept, and gotta say I find it quite good and straightforward. Create Studies with several tasks. Let people participate. I also like the little feedback field. If someone is frustrated or delighted, he/she can hammer it in right away.

The record ideal steps is intended to be done after the task is saved. I have changed the interface to make that apparent and not allow you to record until the task is saved. I noticed that confusion there after testing it myself.

When you participate it creates a new environment (copy of database, and files directory), essentially re-install Drupal. This is done so that multiple participants can all work at the same time without interfering with each other, and even quit between tasks and resume later. What I have been working to complete is the interface to allow the study to specify a base installation that will be used for that study. That would allow you to define user, setup content, etc.

The reason your administrative password did not work is that there are no users in the test environment. Just there to provide the point and get all the data APIs working. Sorry, that isn't clear, but module is still in development. :)

Did it display anything like feedback you may have typed of user path? Part of the problem may be that you didn't enable the plug-in modules and then enable them on the study when you create it. This allows different data to be recorded for different studies. It sounds like no data was recorded, so there was nothing to analyze. :) Things like that need to be made more clear, but by no means is this process simple as it can't be.

Thanks for taking a look. Should have a new release with numerous issues fixed by the middle of this coming week.

Everything mentioned has been fixed.

@eigentor: If you try what I mentioned above and still doesn't work please open a new thread. Thanks all for testing module, feedback is great.

Feed you back. ;)
I finally submitted my session for Drupalcon "User Testing in Drupal" which will have as a central part UTS. So expect to see me repeatedly here and helping out with improving UTS - I need it for the presentation :D

Sounds great!

Amazon, check your gmail. I set up an account for you on my testing site.

@Bojhan: latest beta or dev? Dev has a number of additions.

Jimmy : Beta, although if you want him to see dev, its on the same server as you fixed bugs under the map testing, I am not sure if I should do the update myself?

Beta should be fine.

I would probably recommend waiting until #290271: Review of beta 1 has been resolved before asking for more reviews.