| Fedora Test Days | |
|---|---|
| |
| [Thermostat 1.0] | |
| Date | 2013-05-23 |
| Time | all day |
| Website | Thermostat Website |
| IRC | #fedora-test-day (webirc) |
| Mailing list | test |
What to Test?
Today's installment of Fedora Test Day will focus on Thermostat
As Thermostat 1.0 has been released recently, today's test day can provide a nice way for you to get familiar with the new version, its looks and all the important functionality - especially if you are new to them.
---TODO: insert catchy image here :)
Who's Available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Severin Gehwolf (jerboaa), Omair Majid (omajid), Jon VanAlten (vanaltj)
Prerequisite for Test Day
- An updated Fedora 19 pre-release (physical machine or virtual machine), or a nightly live image
How to test?
- You will either need a physical machine or a virtual machine running a pre-release of Fedora 19
- Make sure that your system is up-to-date. You can update your system using the update manager.
- In particular, you should have the following packages installed:
---TODO: thermostat-in-some-version.fc19
Update Your Machine/VM to Fedora 19
If you are already running Fedora 19 on your physical machine or in a VM make sure to update your system to the latest packages using the update manager. If you don't have the pre-release of Fedora 19 yet, install Fedora 19 Beta and then update to the latest packages. You may also use the live image for our tests (see below)
Live image
Optionally, you may download a non-destructive F19 live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live images can be found here.
Perform Testing
Please perform as many of the test cases listed as you have the time and the resources to complete, and fill out your results in the table below. You do not need a Fedora account to fill in the table.
Planned Tests
- QA:Testcase_thermostat_upgrade
- QA:Testcase_thermostat_service
- QA:Testcase_thermostat_gui
- QA:Testcase_thermostat_shell
- QA:Testcase_thermostat_shell_other
- QA:Testcase_thermostat_web
- QA:Testcase_thermostat_web_remote_with_security
- QA:Testcase_thermostat_remote_mongodb
- QA:Testcase_thermostat_heapdump
- QA:Testcase_thermostat_thread_monitor
Unplanned Testing
As well as running the formal test cases, you can help simply by using Thermostat and/or Thermostat's Eclipse integration and report any problems you come across in the course of your typical use, even if they do not match up with any of the test cases. If unsure if something is a bug feel free to ask in #fedora-test-day.
Test Results
If you have problems with any of the tests, try and report a bug. Thermostat bugs should be reported to Thermostat's Bugzilla. You will need an icedtea bugzilla account to report bugs for Thermostat. Creating one is easy, and we will help you do this if you ask in IRC.
If you are not sure of the appropriate component, please check in IRC before filing, there are many possibilities. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you.
Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one, and the second should be a link to the Smolt profile of the system you tested. For each test case, use the result template to describe your result, following the examples in the Sample user row.
| User | Upgrade | Service | GUI | Shell | Commands | Web Service | Remote Web with Security | Remote Mongodb | Heapdump | Threads | References |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Sample User |  |
|
|
|
 |
 |
|