Calendar:QA Chat:2006-09-21 Log: Difference between revisions

← Older edit

Calendar:QA Chat:2006-09-21 Log (view source)

Revision as of 23:10, 21 September 2006

43 bytes removed , 21 September 2006

no edit summary

Celina63

86

edits

@@ Line 35: / Line 35: @@
 doing that. Possibly to include in the relnotes.
 ctalbert: I'm going to head back to the top of the existing list and go straight
- down it. I think that will be more expedient.
+down it. I think that will be more expedient.
 ctalbert: So, Looks like we can remove 323171 from the urgent blocker category.
 ctalbert: QA Wanted bugs will stay on the list
 ctalbert: (the list is here, by the way: http://wiki.mozilla.org/Calendar:QA_TODO
 ctalbert: Do we need to keep the "Upgrade testing from 0.3a2 and 0.3a1 on the
- list for another week? Sebo did some testing on it.
+list for another week? Sebo did some testing on it.
 ctalbert: What do people think?
 lilmatt: More testing == better until we have something else folks need to
- focus on IMHO
+focus on IMHO
 lilmatt: but if there's more important stuff, we can cut it
 ctalbert: Let's see what people suggest to add.
 ctalbert: I think we'll leave lightning upgrade testing on the list. Bery has
- done a bit of work with it, but we'd like to get more coverage there.
+done a bit of work with it, but we'd like to get more coverage there.
 Bery: good plan
 Bery: I only tested one scenario, after all :)
 ctalbert: The next three have had no takers, so they stay.
 ctalbert: Damian has been really working hard on Litmus. So we'll take his
- completed tasks off.
+completed tasks off.
 ctalbert: I'm going to make those quick edits now. While I'm doing that, does
- anyone have any suggestions for new items to go onto the list?
+anyone have any suggestions for new items to go onto the list?
 Bery: *checks the list for items related to printing*
 celina63: I'm curious about the 3rd item on the current list
 Bery: The primary focus of my users is with printing and task list items
- (and, printing task list items :))
+(and, printing task list items :))
 celina63: how can we test upgrading from the a1 and a2 to 0.3, until 0.3 is
- released?
+released?
 lilmatt: to the nightly
 lilmatt: since all 0.3 will be is a "blessed" nightly
 ctalbert: lilmatt: What's the official story on printing? Your stuff landed in
- sunbird, right?
+sunbird, right?
 lilmatt: Yes.
 lilmatt: If we get time to do the crappy menuitem hack in Lightning, we'll put
- that in as well.
+that in as well.
 Bery: oh, whatever happened to the "hide completed items" checkbox for todo
- lists?
+lists?
 ctalbert: Ok folks can reload the TODO list. It's updated
 ctalbert: I think one of the important things we need to do right now, is to
- verify the fixes that are landing as the blockers get fixed.
+verify the fixes that are landing as the blockers get fixed.
 ctalbert: Bery: I'm not sure
 Bery: One of my users extensively used the task list feature, but when the
- checkbox disappeared it got kind of useless (because his list was so darn long)
+checkbox disappeared it got kind of useless (because his list was so darn long)
 ctalbert: I understand. But, we can't promise any new features at this late
- stage for 0.3.
+stage for 0.3.
 ctalbert: lilmatt: did the timezone database changes go in, or were those
 removed in the last round of triaging?
@@ Line 86: / Line 86: @@
 mikeal: hiya
 Bery: https://bugzilla.mozilla.org/show_bug.cgi?id=310258 - it has a bug report
- already, that's good enough for me
+already, that's good enough for me
 ctalbert: Does anyone have any other ideas of what to Add to the QA Todo list?
- I think I'll add some printing testcases for Sunbird. If those seem to work out
+I think I'll add some printing testcases for Sunbird. If those seem to work out
- okay, then perhaps we can convince dmose to put printing support into
+okay, then perhaps we can convince dmose to put printing support into
- Lightning.
+Lightning.
 ctalbert: Besides, I don't think the Sunbird printing feature has been throughly
- tested yet.
+tested yet.
 ctalbert: mikeal: the ToDo list in question is at: http://wiki.mozilla.org/Calendar:QA_TODO
 mikeal: ok, thanks
 ctalbert: np
 ctalbert: Speak up if anyone has ideas of things to add (or remove) from that
- list. I want to go on to the last agenda item.
+list. I want to go on to the last agenda item.
-ctalbert: I believe that Damian wrote that, and he's not here at the moment. Essentially, he's wanting systematic way to scour the buglists for potential
+ctalbert: I believe that Damian wrote that, and he's not here at the moment.
- litmus testcases.
+Essentially, he's wanting systematic way to scour the buglists for potential
+litmus testcases.
 mikeal: do you guys have caldav tests written yet?
 mikeal: sorry, automated caldav tests
 ctalbert: Not very many tests written, and no automated ones.
 ctalbert: jminta, lilmatt: would there be anyproblem with adding a whiteboard
- item to designate "potential testcase" in bugzilla?
+item to designate "potential testcase" in bugzilla?
 mikeal: ok, can you point me at docs on how to write/run automated
 sunbird/lighting tests
@@ Line 119: / Line 120: @@
 xFallenAngel: there is a testcase keyword
 mikeal: most of the current server test tools just make raw HTTP requests, the
- web UI is tested with Selenium and the json-rpc backend it tested with a raw
+web UI is tested with Selenium and the json-rpc backend it tested with a raw
- HTTP tool
+HTTP tool
 ctalbert: Yes, there's a lot of discussion in the mozilla QA side that is trying
- to standarize on a common set, but I don't believe that has converged. Let's
+to standarize on a common set, but I don't believe that has converged. Let's
- talk about this at the end of the calendar QA meeting, please.
+talk about this at the end of the calendar QA meeting, please.
 mikeal: and then Chandler has it's own scripting layer built on wx that we use
- to automate everything using the UI
+to automate everything using the UI
 mikeal: ok
 ctalbert: xFallenAngel: Maybe then it would be best to use that keyword
 ctalbert: I think using that keyword would be the right approach. I'll take this
- up with dmose and any bugzilla admins I need to.
+up with dmose and any bugzilla admins I need to.
 xFallenAngel: does this keyword need to be set by a developer, or can it be
- requested/set by anyone?
+requested/set by anyone?
 jminta: the testcase keyword means a testcase exists for the bug already
 ctalbert: I just want to encourage everyone to add that keyword to bugs with
- good Steps to Reproduce that would make sense to be testcases that would be run
+good Steps to Reproduce that would make sense to be testcases that would be run
- on an ongoing basis.
+on an ongoing basis.
 ctalbert: xFallenAngel: That's the kind of thing I need to figure out.
 ctalbert: jminta: then would a whiteboard item be better?
 ctalbert: xFallenAngel: Ideally, I want both developer and QA to be able to set
- the attribute.
+the attribute.
 jminta: sure [needs testcase] or [testcase wanted]
 ssitter: xFallenAngel: see https://bugzilla.mozilla.org/describekeywords.cgi
- for meaning of keywords
+for meaning of keywords
 jminta: anyone with editbugs should be able to do that
 ctalbert: Cool. I'll suggest those to Damian then.
 ssitter: mmh, it's not clear if you want a testcase attached to bug (e.g. ics
- sample) or a new testcase in litmus
+sample) or a new testcase in litmus
 ctalbert: [litmus testcase wanted]
 ctalbert: how's that ^^^
 xFallenAngel: well, if the bug already has most steps for the testcase, they
- litmus testcase wanted sounds more like there is something missing. I suggest
+litmus testcase wanted sounds more like there is something missing. I suggest
- [valid litmust testcase]
+[valid litmust testcase]
 xFallenAngel: -t
 ctalbert: sounds good to me.
 ctalbert: Anyone else have a thought about it? It needs to be something we can
- all remember easily.
+all remember easily.
 ctalbert: Going once....
 celina63: sounds good to me
 ctalbert: ssitter, what do you think about it?
 xFallenAngel: we could note it on the wiki somewhere, then we can look it up if
- we forget?
+we forget?
 ssitter: maybe [litmus testcase wanted] and  [has litmus testcase]?
 ctalbert: xFallenAngel: we will.
@@ Line 168: / Line 169: @@
 ctalbert: That too
 ctalbert: I think I'm going to change my vote to ssitter's proposal. I like the
- idea of tracking what we've put into Litmus. Because Litmus isn't all that good
+idea of tracking what we've put into Litmus. Because Litmus isn't all that good
- at keeping track of these things yet.
+at keeping track of these things yet.
 ssitter: or instead of [has litmus testcase] just create a bug comment like
- 'litmus testcase 12345 created'
+'litmus testcase 12345 created'
 ssitter: this helps to keep status whiteboard clean
 ctalbert: good idea
 ctalbert: Does anyone object to that idea?
 ctalbert: Does anyone have anything else to add to the QA TODO list. I've made
- the updates we discussed.
+the updates we discussed.
 ctalbert: Okay. Anyone have anything else to discuss, we have about four minutes
- left to this meeting. (Besides automated testing - we'll get to that next).
+left to this meeting. (Besides automated testing - we'll get to that next).
 * ctalbert hasn't forgotten mikeal
 mikeal: :)
-ctalbert: Ok. Don't forget to update the ToDo list with the things you do. Thanks for all your time.
+ctalbert: Ok. Don't forget to update the ToDo list with the things you do.
+Thanks for all your time.
 ctalbert: Happy testing.
 * ctalbert takes off his "official calendar-qa meeting hat"
 </pre>