Proposing a new draft release validation test case:
https://fedoraproject.org/wiki/User:Adamwill/Draft_QA_Testcase_desktop_termi...
this is a fairly simple test case that just checks that a terminal application works in a desktop environment. It would be added to the desktop matrix along with the browser test case, to cover the lack of a test case to enforce the terminal part of the Alpha criterion "It must be possible to run the default web browser and a terminal application from all release-blocking desktop environments."
Comments, improvements, suggestions etc welcome as always! As this is pretty straightforward I'm planning to put it into production pretty soon if there's no negative feedback.
Proposing a new draft release validation test case:
https://fedoraproject.org/wiki/User:Adamwill/Draft_QA_Testcase_desktop_termi...
Looks good.
"and run and quit some common applications" -- It's not exactly clear here that the applications should be run _from_ the terminal, but it's mostly obvious.
On 07/30/2013 10:22 PM, Adam Williamson wrote:
Proposing a new draft release validation test case:
https://fedoraproject.org/wiki/User:Adamwill/Draft_QA_Testcase_desktop_termi...
this is a fairly simple test case that just checks that a terminal application works in a desktop environment. It would be added to the desktop matrix along with the browser test case, to cover the lack of a test case to enforce the terminal part of the Alpha criterion "It must be possible to run the default web browser and a terminal application from all release-blocking desktop environments."
Comments, improvements, suggestions etc welcome as always! As this is pretty straightforward I'm planning to put it into production pretty soon if there's no negative feedback.
Stuff this in beta not alpha
Desktop Application testing do not belong in alpha...
JBG
On Wed, 2013-07-31 at 17:28 +0000, "Jóhann B. Guðmundsson" wrote:
On 07/30/2013 10:22 PM, Adam Williamson wrote:
Proposing a new draft release validation test case:
https://fedoraproject.org/wiki/User:Adamwill/Draft_QA_Testcase_desktop_termi...
this is a fairly simple test case that just checks that a terminal application works in a desktop environment. It would be added to the desktop matrix along with the browser test case, to cover the lack of a test case to enforce the terminal part of the Alpha criterion "It must be possible to run the default web browser and a terminal application from all release-blocking desktop environments."
Comments, improvements, suggestions etc welcome as always! As this is pretty straightforward I'm planning to put it into production pretty soon if there's no negative feedback.
Stuff this in beta not alpha
Desktop Application testing do not belong in alpha...
That's determined by the release criterion, not the test case. If you want to propose moving the criterion from Alpha to Beta, start a separate thread for that. But personally I'd prefer it to stay at Alpha; it does make sense to require the two most crucial apps for any desktop to work at Alpha.
On 07/31/2013 05:33 PM, Adam Williamson wrote:
On Wed, 2013-07-31 at 17:28 +0000, "Jóhann B. Guðmundsson" wrote:
On 07/30/2013 10:22 PM, Adam Williamson wrote:
Proposing a new draft release validation test case:
https://fedoraproject.org/wiki/User:Adamwill/Draft_QA_Testcase_desktop_termi...
this is a fairly simple test case that just checks that a terminal application works in a desktop environment. It would be added to the desktop matrix along with the browser test case, to cover the lack of a test case to enforce the terminal part of the Alpha criterion "It must be possible to run the default web browser and a terminal application from all release-blocking desktop environments."
Comments, improvements, suggestions etc welcome as always! As this is pretty straightforward I'm planning to put it into production pretty soon if there's no negative feedback.
Stuff this in beta not alpha
Desktop Application testing do not belong in alpha...
That's determined by the release criterion, not the test case. If you want to propose moving the criterion from Alpha to Beta, start a separate thread for that. But personally I'd prefer it to stay at Alpha; it does make sense to require the two most crucial apps for any desktop to work at Alpha.
How do you define a terminal as a crucial app for any desktop?
Let alone at alpha when the user can always boot into the multi-user target for a terminal and <ctrl><alt>F2?
JBG
On Wed, 31 Jul 2013, "Jóhann B. Guðmundsson" wrote:
How do you define a terminal as a crucial app for any desktop?
Let alone at alpha when the user can always boot into the multi-user target for a terminal and <ctrl><alt>F2?
and that keystroke sequence works in a VM across a TLS protected connection, just how? We probably deploy 500 VMs to each new tangible one
-- Russ herrold
On Wed, 2013-07-31 at 17:54 +0000, "Jóhann B. Guðmundsson" wrote:
On 07/31/2013 05:33 PM, Adam Williamson wrote:
On Wed, 2013-07-31 at 17:28 +0000, "Jóhann B. Guðmundsson" wrote:
On 07/30/2013 10:22 PM, Adam Williamson wrote:
Proposing a new draft release validation test case:
https://fedoraproject.org/wiki/User:Adamwill/Draft_QA_Testcase_desktop_termi...
this is a fairly simple test case that just checks that a terminal application works in a desktop environment. It would be added to the desktop matrix along with the browser test case, to cover the lack of a test case to enforce the terminal part of the Alpha criterion "It must be possible to run the default web browser and a terminal application from all release-blocking desktop environments."
Comments, improvements, suggestions etc welcome as always! As this is pretty straightforward I'm planning to put it into production pretty soon if there's no negative feedback.
Stuff this in beta not alpha
Desktop Application testing do not belong in alpha...
That's determined by the release criterion, not the test case. If you want to propose moving the criterion from Alpha to Beta, start a separate thread for that. But personally I'd prefer it to stay at Alpha; it does make sense to require the two most crucial apps for any desktop to work at Alpha.
How do you define a terminal as a crucial app for any desktop?
Let alone at alpha when the user can always boot into the multi-user target for a terminal and <ctrl><alt>F2?
Honestly, just in practical terms: it's one of the main things I'd expect to use in testing a pre-release, and that was the consensus when we initially drafted that criterion.
Like I said, if you want to propose changing it, please start a new thread, it'd be nice not to derail this one. This one is about the proposed test case. We need the test case whatever level the criterion is at.
On Tue, 2013-07-30 at 15:22 -0700, Adam Williamson wrote:
Proposing a new draft release validation test case:
https://fedoraproject.org/wiki/User:Adamwill/Draft_QA_Testcase_desktop_termi...
this is a fairly simple test case that just checks that a terminal application works in a desktop environment. It would be added to the desktop matrix along with the browser test case, to cover the lack of a test case to enforce the terminal part of the Alpha criterion "It must be possible to run the default web browser and a terminal application from all release-blocking desktop environments."
Comments, improvements, suggestions etc welcome as always! As this is pretty straightforward I'm planning to put it into production pretty soon if there's no negative feedback.
I've gone ahead and put this into production at https://fedoraproject.org/wiki/QA:Testcase_desktop_terminal . Johann never did make a proposal to drop the criterion, and the test case is useful regardless of whether it's release blocking or not. No-one seemed to object to the substance of the test case.
-
Adam Williamson -
Jóhann B. Guðmundsson -
Kamil Paral -
R P Herrold