QA に関わっていらっしゃるみなさん、こんにちは。
OO.o の QA Lead Andre Schnabel さんが TCM のシナリオ (以前の TCM の
Writer-1 とか
Impress といったカテゴリに相当するテスト単位) "OOo release sanity" を提案
しています。これは最低限のサニティチェックを目的とした物で Smoke Test の
代わり
といってもいいかもしれません。rc の受け入れ検査に関しては今後これを元に
行われるように
なる可能性があります。
http://www.sunvirtuallab.com/tcm2/opensource/tcm_login.cgi?tcm_config=newooo
から ja_guest / 123 でログインして、"2. Test Scenario maintenance" ->
"OOo release sanity" で内容を見ることが出来ます。
(テストケースが英語で出てしまうのはバグだと思われます)
現在コメントを求めている段階ですので、最低限これもやった方がいいなどコメ
ントありましたら
お願いします。
石村
--- Begin Message ---
Hi,
I'v created a new scenario in TCM, called "OOo release sanity". I'd like to use
this as the absolut minimum of tests, that a build needs to pass to be approved for
release.
This should help in situations like we have with 2.0.3:
- a series of RC's has already been tested
- a small amount of stoppers needs to be fixed
- running the full tests again would take a lot of time
- running no tests at all would break our QA policy
I'm not shure, what test cases should be put to the scenario. The current set
is my first attemt .. and as always, at the one hand it seems not enough to be
shure we have no bugs .. at the other it seem to be to many tests to be able to
go through the scenario quickly.
Comments are welcome (no problem, if they would take some time, I know, native
lang teams are still busy with 2.0.3 testing).
andré
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--- End Message ---
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
