Ticket #204 (closed task: fixed)

Opened 3 years ago

Last modified 2 years ago

Create test case for artwork

Reported by: adamwill Owned by: adamwill
Priority: major Milestone: Fedora 16
Component: Wiki Version:
Keywords: Cc: rhe, robatino
Blocked By: Blocking:

Description

As per #151, we are missing a test case for the Alpha release criterion "The default Fedora artwork must either refer to the current Fedora release under development (Fedora 16), or reference an interim release milestone (e.g. Alpha or Beta). If a release version number is used, it must match the current Fedora release under development. This includes artwork used in the installer, firstboot, graphical boot, graphical login and desktop background." (and also for the Final criterion "The proposed final Fedora artwork must be included and enabled by default for the installer, graphical boot, firstboot, graphical login and desktop background. All Fedora artwork must be consistent with the proposed final theme, and if any artwork contains a graphical version number, the version number used must match the Fedora release number. Generic release artwork (e.g. Alpha, Beta, Development) must not be used for the final release"). We should create one or two test cases to cover these criteria and add them to the desktop matrix.

Change History

comment:1 Changed 3 years ago by rhe

  • Owner changed from adamwill to adamwill, rhe
  • Cc rhe, robatino added

Yeah, I need add an artwork test to the install matrix too.

comment:2 Changed 3 years ago by adamwill

  • Owner changed from adamwill, rhe to adamwill
  • Status changed from new to assigned

Rather than adding specific artwork test cases, I have added artwork considerations to the firstboot and startup test cases:

https://fedoraproject.org/wiki/QA:Testcase_base_startup https://fedoraproject.org/wiki/QA:Testcase_base_firstboot

comment:3 Changed 3 years ago by rhe

Referencing to what you created, I've also added artwork check for installer in the anaconda graphical test.

comment:4 Changed 2 years ago by adamwill

  • Status changed from assigned to closed
  • Resolution set to fixed

I think we can consider this fixed now, between the three referenced test cases.

Note: See TracTickets for help on using tickets.