On 08/09/2011 05:17 PM, ext-iekku.pyl...@nokia.com wrote:
Hi Jeff,
Sounds reasonable to me. There's no reason to keep on releasing if there's not
enough changes.
Other thing I would talk about is the MCTS weekly bug triage. There hasn't been
so much new bugs to triage that the meeting is need
Hi,
Since there is less and less changes in MCTS... latest two MCTS releases
fixed one test type bug... I'd like to propose to change the biweekly
MCTS release to on-demand release.
Please let me know if there is any concern. Thanks.
Bests
Jeff
___
On 08/09/2011 04:55 PM, Zhao, Fan wrote:
Hi all,
It's discussed in today's QA meeting about the proposal to make QA meeting on
demand instead of on weekly basis, and basically all attendees of today's
meeting second the proposal, so I'd like to look for broader feedbacks here.
The motivation t
On 08/02/2011 03:32 PM, Jussi Saavalainen wrote:
On Tuesday 02 August 2011 05:35:35 Jeff Zheng wrote:
On 08/01/2011 01:31 PM, Jeff Zheng wrote:
On 07/22/2011 10:28 AM, Zheng, Jeff wrote:
Hi all,
This is to announce that MCTS release 1.3.5 are now complete.
This release update test type
On 08/01/2011 01:31 PM, Jeff Zheng wrote:
On 07/22/2011 10:28 AM, Zheng, Jeff wrote:
Hi all,
This is to announce that MCTS release 1.3.5 are now complete.
This release update test type according to new test definition for
mcts- test suites. We wish the update for BLTS and MWTS be available
in
On 07/22/2011 10:28 AM, Zheng, Jeff wrote:
Hi all,
This is to announce that MCTS release 1.3.5 are now complete.
This release update test type according to new test definition for
mcts- test suites. We wish the update for BLTS and MWTS be available
in next release.
(Change title to get focus)
Hi Timo,
On 07/20/2011 02:23 PM, Timo Härkönen wrote:
Besides having the test type named as "UserExperience" would cause the
names to be inconsistent. The current names are visible for example
here:
https://meego.gitorious.org/meego-quality-assurance/test-definition/blobs/master/src/data/testde
On 07/13/2011 03:44 PM, Fu, Elva wrote:
Done.
New test
types"FunctionalPositive|FunctionalNegative|Security|Performance|Reliability|Maintainability|Portability"
were added to tl.meego.com.
Thanks Elva.
Now we need to fix bug 17877... We just need to fix it in MCTS-1.3 since
test-definition
/
I would like to express my thanks to developers of this release:
Fu, Yi
Jeff Zheng
Bests
Jeff
___
MeeGo-qa mailing
On 07/07/2011 01:37 PM, Fu, Elva wrote:
Elva, I think these test types will be in tests.xml if testlink export
test suite to xml, is it correct?
Bests
Jeff
Yes, correct. :-)
thanks,
Elva
Great, thanks!
Bests
Jeff
___
MeeGo-qa mailing list
MeeGo-qa@
On 07/07/2011 10:00 AM, Fu, Elva wrote:
Hello Christophe,
I would like to raise this topic again as Jeff had no feedback until now
and there is no real progress regarding the submitted bugs:
17768 Test types update in tl.meego.com
17877 Test types update in MCTS
18365 Test types update i
On 06/15/2011 03:56 PM, Timo Härkönen wrote:
On Wed, 2011-06-15 at 10:19 +0300, Jeff Zheng wrote:
On 06/15/2011 03:06 PM, Pelkonen Tuomo wrote:
So should a test plan have different name than tests.xml, for example
testplan.xml, to avoid confusion and to separate purpose of these files?
http
On 06/15/2011 03:37 PM, Pelkonen Tuomo wrote:
Again I'd like to repeat that one tests.xml rule defined in release criteria
and guideline for a long time:
http://wiki.meego.com/Quality/TestSuite/MCTS/MCTS_Release_Process
http://wiki.meego.com/Quality/TestSuite/MCTS/MCTS_Development_Guideline
The
On 06/15/2011 03:06 PM, Pelkonen Tuomo wrote:
So should a test plan have different name than tests.xml, for example
testplan.xml, to avoid confusion and to separate purpose of these files?
http://wiki.meego.com/Quality/QA-tools/Test_plan
This is another topic. I just prefer to talk about tests.x
On 06/15/2011 02:43 PM, Tuomo Pelkonen wrote:
Just found that there is no tests.xml in mwts packages, furthur
checking
shows that all mwts assets move tests.xml to tests-all.xml and don't
include tests-all.xml into mwts packages.
Since tests.xml is reserved name for mcts test suites, I report
On 06/15/2011 02:34 PM, Pelkonen Tuomo wrote:
Hi,
This is the issue we have been earlier discussing in bug 18414.
Previously, our test modules included tests.xml only to represent all available
test scripts provided with the test module. Anyhow, this file does not
represent test plan as descr
On 06/15/2011 02:10 PM, Fu, Elva wrote:
-Original Message-
From: meego-qa-boun...@lists.meego.com
[mailto:meego-qa-boun...@lists.meego.com] On Behalf Of Jeff Zheng
Sent: Wednesday, June 15, 2011 11:09 AM
To: meego...@meego.com
Subject: [Meego-qa] No tests.xml in mwts packages
Hi,
Just
Hi,
Just found that there is no tests.xml in mwts packages, furthur checking
shows that all mwts assets move tests.xml to tests-all.xml and don't
include tests-all.xml into mwts packages.
Since tests.xml is reserved name for mcts test suites, I reported a
critical bug 19174 to track this iss
On 06/13/2011 08:24 PM, Timo Härkönen wrote:
On Fri, 2011-06-10 at 06:43 +0300, Zheng, Jeff wrote:
Hi
I found there is defintion for test set, there is a term "set" in
test-definition, but I understand that it refers to
http://wiki.meego.com/Quality/TestSetGuideline
test-definition (the t
19 matches
Mail list logo
