[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Feature Test Plans (was Re: [F-10 Feature?] Nodoka notification theme)

> Here's the deal with Test Plans: A Test Plan is a document that tells
> the testers how to test your feature.
> While writing your Test Plan, pretend that you have an intern whose job
> it is to test new features that land in Fedora releases. This brave,
> brave soul has a few years' experience as a Fedora user and basic
> familiarity with using the commandline to configure stuff, install
> packages, and so on. 
> Your job is to tell this person how they can test your cool new feature,
> so they can either a) tell their friends about how cool it is, or b)
> tell you (via bugzilla) if it breaks.
> A good Test Plan should answer these four questions:
> 0. What special hardware / data / etc. is needed (if any)?
> 1. How do you prepare your system to test this feature? What packages
> need to be installed, config files edited, etc.?
> 2. What specific actions do you perform to check that the feature is
> working like it's supposed to?
> 3. What are the expected results of those actions?
> Your answers can be short: "get a bluetooth keyboard and yum install
> bluez-gnome newer than 0.25" answers question 0 and 1 just fine. But
> they need to be complete and explicit: "Get an appropriate keyboard and
> install the new packages" is not helpful.
> Soon I'm going to start tracking down Feature owners whose Feature pages
> don't tell me how to test their stuff. I'm happy to help write good test
> plans, but you can save a lot of trouble by getting one ready *before* I
> come bother you on IRC / by email / outside your window at night[1].
> -w
> [1] Only kidding. Probably.

Thanks for the info, it really makes my life a lot easier ;-) Does this
test plan looks good (edited in wiki as well)?

Test Plan 
      * Install notification-daemon-engine-nodoka
      * Testing the engine 
              * Set gconf '/app/notification-daemon/theme' key to
              * Use various software that show notification bubbles
              * Test either with compositing enabled or disabled (the
                engine behaves slightly different based on the
                availability of true transparency)
              * Watch if the bubbles are displayed correctly
      * Testing theme selection via gconf 
              * Switch gconf '/app/notification-daemon/theme' key
                between 'nodoka' and 'standard'
              * Watch if the change is applied correctly - i.e. the
                engine is set properly and applications continue showing
                notification bubbles
              * Known issues - Bug 455289: Notification daemon crashes
                after changing theme
      * Testing theme selection via appearances caplet 
              * Switch between various themes in the appearances caplet
                (using the latest rawhide control-center rpm package)
              * Look if the notification theme is changed properly (look
                into /usr/share/themes/*/index.theme files for
                NotificationTheme key, if not set, notification theme
                should be set to standard, otherwise it should use the
                value of the key)
              * Try customizing the selected theme and see if the
                notification theme stays unchanged
              * Known issues - Bug 455329: Notification theme is reset
                to standard when theme is customized
      * Report any issues at rhbz


Attachment: signature.asc
Description: This is a digitally signed message part

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]