Run testdaybot for the next Test Day on 2015-01-23

[whimboo]

@ashughes1 as far as I can remember the next testday is this Friday. I would like to have the testday bot running through the day. Please let me know about details so we can get it setup together.

I will get the bot running on mozqa.com under my personal account. If all is working fine we can make it a service on that host.

[ghost]

The information is posted to QMO:
http://quality.mozilla.org/2015/01/firefox-36-beta-3-testday-january-23rd/

[galgeek]

Hi @ashughes1 and @whimboo!

I've left my current code, including today's two PRs, running in #testdaybotTest, using the nick _TestDayBotTestBot, which shouldn't interfere with your running the bot in #qa.

The command to schedule Friday's test day should be something like this:

:next 2015-01-23T08:00Z 2015-01-24T01:00Z https://etherpad.mozilla.org/testday-20150123 Welcome to today’s Test Day!

[whimboo]

No, the format of the :next command should be:

:next 2015-01-23T07:00Z 2015-01-24T01:00Z https://etherpad.mozilla.org/testday-20150123 Firefox 36.0 beta 3 Testday

I will bring up the bot and schedule this event. For the remaining feedback issues fixed, we can restart the bot at anytime once those have been landed.

[galgeek]

Hi, @whimboo!

If the updated topic code is in place, you'll likely want to switch the topic in the :next command to just "Firefox 36.0 beta 3"

[whimboo]

Beside issue #54 all feedback has been incorporated. @galgeek mentioned that she might be able to also fix this PR. So I will wait with updating the bot until it has been merged.

Other things I have to do:

• Register _Testdaybot against nickserv and update the config file for the password

I will do this tomorrow morning before the testday starts.

[whimboo]

All is done and the bot is running in #qa for todays testday. He has auto-op when joining the channel. @ashughes1, I will send you the password for backup via email.

Please let me know if anything makes problems.

[whimboo]

@ashughes1 and @ctalbert I wonder if we could get some feedback in how the testday went and how helpful the new bot was. Also it would be good if there are other important things to get fixed. Thanks.

[ghost]

I'll be sure to provide you with feedback as soon as I've had a chance to sit down with Florin to chat about it.

[ghost]

Florin mentioned in the last meeting that he hadn't much opportunity to play with Testdaybot. I suggest we cc him on this issue and add an action item for him to try it out next time to provide feedback.

[whimboo]

I have pinged Florin again on IRC. If we don't get an update on this issue until end of this week I will assume that everything works as expected as of now.

[FlorinMezei]

We (the manual QE team) have used the testday bot for a couple of testdays now and it seems to work rather well. Very useful in getting support info and advertising the event on IRC.

Two very small improvements that I would like:

1. When running ":stats" sort the active people by "most active" to "least active" - currently randomly listed.
2. When setting the ":next" testday make "time" errors more explicit:
   a) start time in the past
   b) start time after end time
   Currently we get the same generic error that time is invalid and have to hunt down where the issue is.

[whimboo]

Thank you Florin! That sounds good. Those two issues you are mentioning here are more enhancements. We cannot currently work on those but we can have them mentored and let other members of the community work on that.

See some inline details:

1. When running ":stats" sort the active people by "most active" to "least active" - currently randomly listed.

Filed as issue #73.

1. When setting the ":next" testday make "time" errors more explicit:
   a) start time in the past
   b) start time after end time
   Currently we get the same generic error that time is invalid and have to hunt down where the issue is.

Filed issue #74.

Given that no major pain points came up I will mark this issue as fixed. Thanks for your feedback!