m (→Test Cases) |
|||
| Line 67: | Line 67: | ||
== Test Cases == | == Test Cases == | ||
=== Basic === | |||
# [[QA:Testcase_JBoss_AS_Install_and_run|Install and run]] | |||
=== Management === | |||
TBD | |||
=== Deployment === | |||
TBD | |||
== Test Results == | == Test Results == | ||
Revision as of 13:39, 3 April 2012
| Fedora Test Days | |
|---|---|
| |
| JBoss AS 7 | |
| Date | 17.04.2012 |
| Time | all day |
| Website | QA/Fedora_17_test_days |
| IRC | #fedora-test-day (webirc) |
| Mailing list | java-devel |
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.
What to test?
JBoss Application Server 7
Today's instalment of Fedora Test Day will focus on JBoss Application Server. This time we're testing version 7.1.0 which is planned as a Feature for Fedora 17.
JBoss Application Server 7 is the latest release in a series of JBoss Application Server offerings. JBoss Application Server 7, is a fast, powerful, implementation of the Java Enterprise Edition 6 specification. The state-of-the-art architecture built on the Modular Service Container enables services on-demand when your application requires them.
For more information about JBoss AS please refer to its homepage.
Custom build
The included JBoss Application Server is a custom build. It means that it's not exactly the same as upstream's distribution. The Fedora version includes only JEE 6 web-profile. The main reson for that were time constraints.
Although we tried to make it happen, at this point there is no Hibernate 4 (JPA2 implementation) included in Fedora. Sad, but true. The reason for that are issues with packaging Gradle (build tool used in Hibernate). For more info please contact Carlo de Wolf.
JBoss AS will be extended with new updates to the full version over the time.
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Marek Goldmann (mgoldmann on IRC)
Prerequisite for Test Day
- An Fedora 17 pre-release with all updates from
updates-testinginstalled, Rawhide (tips on installing Rawhide below), or a nightly live image - Time
- (optional) Your hardware profile uploaded to Smolt according to these instructions
- (optional) Beer (if you're adult)
How to test?
High level details on how a contributor can get involved. This can include (but not limited to):
- Areas to target with exploratory testing
- A list of pre-defined test cases to execute
- How to report back results
Here's another common chunk (again, replace XX as above):
Update your machine
If you're running Fedora XX, make sure you have all the current updates for it installed, using the update manager. If you want to try Rawhide, see the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. Or:
Live image
Optionally, you may download a non-destructive Rawhide live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live images can be found here.
Test Cases
Basic
Management
TBD
Deployment
TBD
Test Results
Construct a table or list to allow testers to post results. Each column should be a test case or configuration, and each row should consist of test results. Include some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:
If you have problems with any of the tests, report a bug to Bugzilla usually for the component udisks, or gnome-disk-utility for bugs in the Palimpsest graphical front end itself. 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 enter your result, as shown in the example result line.
| User | Smolt Profile | Sample test 1 | Sample test 2 | Sample test 3 | Sample test 4 | References |
|---|---|---|---|---|---|---|
| Sample User | HW |  |
 |
 |