[Fedora QA] #76: Use two methods to specify install source

[Fedora QA]

#76: Use two methods to specify install source
--------------------------+-------------------------------------------------
  Reporter:  rhe          |       Owner:  rhe      
      Type:  enhancement  |      Status:  new      
  Priority:  major        |   Milestone:  Fedora 14
 Component:  Wiki         |     Version:           
Resolution:               |    Keywords:           
--------------------------+-------------------------------------------------
Comment (by rhe):

 Replying to [comment:10 jlaska]:
 > Replying to [comment:8 rhe]:
 > > I'll continue thinking about other approaches of this grouping idea.
 Anyone please feels free for advice. Thanks.
 >
 > Inspired by the format AdamW uses for Test Days, I was curious how it
 might look to have 2 large tables.
 >  1. A table listing all general tests where the media used is not
 critical.  Basically the same format we used for F-13.
 >  2. Another table listing the tests that are specific to different
 media.  I'm adopting a similar format to that used in test days,
 >
 > For a quick example of table#2, checkout
 [https://fedoraproject.org/wiki/User:Jlaska/Draft#Another_Approach
 User:Jlaska/Draft#Another_Approach]

 I thought about this approach before when I recalled
 [https://fedoraproject.org/wiki/Is_anaconda_broken_roadmap
 Is_anaconda_broken_roadmap], I feel comfortable about what it looks like,
 but one big problem is that editing the results would become more
 difficult for testers, since there are 10 frames to be filled in each row.
 Do you think the testers can adapt it?[[BR]]


 Besides, I further divided this approach into two:
 [https://fedoraproject.org/wiki/User:Rhe/Draft#Another_Approach1 App1] and
 [https://fedoraproject.org/wiki/User:Rhe/Draft#Another_Approach2 App2]. As
 you can see, App1 combined all test cases of one text area into "one
 case", which makes the table more brief, while App2 (unfinished) seems too
 grey and like a puzzle since many times only one media is suitable for a
 case.

-- 
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/76#comment:11>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance