Test Day on August 8 2017 » History » Sprint/Milestone 13
email@example.com, 07/26/2017 05:07 PM
# Test Day for 2.14 and pulp deb plugin
## Join us on August 8, 2017 to test the 2.14 release and the new pulp_deb plugin!
> - How to join
> - What to test
> - Who is available for help
> - Prerequisites for test day
> - Resources ( where to get RPMs, fedora images, etc)
> - How to test
> - Confirming existing issues
> - Filing new issues
> - How to report results
### Can't make the date?
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 here on https://pulp.plan.io, and report your results as detailed in "How to report results" section below.
## How to join
Join the [#pulp channel on freenode](http://irc.netsplit.de/channels/details.php?room=%23pulp&net=freenode)
You can join via your favorite IRC client, or either of the two web clients below:
[pulp channel on irc2go](http://en.irc2go.com/webchat/?net=freenode&room=pulp)
[freenode webchat](https://webchat.freenode.net/) (you will need to specify the channel as "#pulp")
Specify a nickname that you would like to go by, and keep it safe for work please!
Many people choose something close to their name, as in Elijah's nickname is "elijah_d".
## == What to test? ==
The August 8th Pulp Test Day will focus on the [Pulp 2.14 beta release](http://docs.pulpproject.org/en/2.14/testing/user-guide/release-notes/2.14.x.html#pulp-2-14-release-notes) and the new [pulp debian plugin](https://github.com/pulp/pulp_deb/#debian-support)
Testers can walk through a manual upgrade from an existing pulp install, installing manually both pulp and the pulp_debian plugin,
or can skip testing installation (and the documentation for that) by using ansible to install and moving on to confirming functionality of the product, that bugs that were fixed in the release are indeed fixed, or other exploratory testing.
## == Who's available ==
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion.
### Quality Engineering
- Elijah DeLee (email: firstname.lastname@example.org irc: elijah_d)
- Preethi Thomas (email: email@example.com irc: preethi)
- Kersom Oliveira (email: firstname.lastname@example.org irc: kersom)
- Jeremy Audet (email: email@example.com irc: Ichimonji10)
Specifically in the case of problem related to test day wiki, please reach out to Elijah DeLee at firstname.lastname@example.org or on irc (nick: elijah_d)
## == Prerequisite for Test Day ==
- Fedora 24, 25, or 26 or RHEL 7 machine (or VM)
- Root access on the system
If you would like to spin up a Fedora VM for testing, see [[Virtualization quickstart]] for a guide on some ways to spin up a VM on your machine for testing.
## == Resources (where to get RPMs, fedora images, etc) ==
The Pulp 2.14 beta repository is included in the pulp repo files:
https://repos.fedorapeople.org/repos/pulp/pulp/fedora-pulp.repo for fedora 24 & 25
https://repos.fedorapeople.org/repos/pulp/pulp/rhel-pulp.repo for RHEL 7
You can find fedora images here:
## == How to test? ==
### == Run the tests ==
If you'd like to run the integration test suite, [pulp-smash](https://github.com/PulpQE/pulp-smash) or any individual tests, you can run them either locally on the pulp_server or remotely from any machine that can SSH into the pulp_server.
For docs on pulp-smash, see http://pulp-smash.readthedocs.io/en/latest/ where you can find instructions on how to install and configure pulp-smash to run against your pulp install.
If you have trouble, email us or ping us on IRC and we can help you get it set up!
### == Exploratory testing ==
You can help out by playing around with the tool in whatever ways you can think of: try out all the things you can find.
Get creative! Any problems you find please file a bug, or report to the IRC channel.
As a user, you should be able to Create, Read, Update, and Delete repositories and the data within. Is this the case? Where do you run into trouble?
## == Confirming existing issues ==
There are three different ways you can use existing issues.
### 1\. Confirm that user stories marked "closed" work
You can find closed "user stories" [here](https://pulp.plan.io/issues?c%5B%5D=project&c%5B%5D=tracker&c%5B%5D=status&c%5B%5D=priority&c%5B%5D=subject&c%5B%5D=assigned_to&c%5B%5D=updated_on&f%5B%5D=status_id&f%5B%5D=tracker_id&f%5B%5D=&group_by=project&op%5Bstatus_id%5D=c&op%5Btracker_id%5D=%3D&page=1&set_filter=1&t%5B%5D=&utf8=%E2%9C%93&v%5Btracker_id%5D%5B%5D=3)
### 2\. Confirm that bugs fixed in the 2.14 release are indeed fixed!
[Bugs fixed in 2.14](https://pulp.plan.io/projects/pulp/issues?c%5B%5D=tracker&c%5B%5D=status&c%5B%5D=priority&c%5B%5D=cf_5&c%5B%5D=subject&c%5B%5D=author&c%5B%5D=assigned_to&c%5B%5D=cf_3&f%5B%5D=cf_4&f%5B%5D=tracker_id&f%5B%5D=&group_by=&op%5Bcf_4%5D=%3D&op%5Btracker_id%5D=%3D&set_filter=1&sort=priority%3Adesc%2Ccf_5%3Adesc%2Cid%3Adesc&utf8=%E2%9C%93&v%5Bcf_4%5D%5B%5D=2.14.0&v%5Btracker_id%5D%5B%5D=1)
### 3\. Validate existence of outstanding bugs
Validate existence of bugs, and if it seems suitable for for pulp-smash tests, file an issue on [pulp-smash github issues](https://github.com/PulpQE/pulp-smash/issues)
[Open issues with no pulp-smash issue filed](https://pulp.plan.io/projects/pulp/issues?utf8=%E2%9C%93&set_filter=1&f%5B%5D=tracker_id&op%5Btracker_id%5D=%3D&v%5Btracker_id%5D%5B%5D=1&f%5B%5D=status_id&op%5Bstatus_id%5D=o&f%5B%5D=cf_34&op%5Bcf_34%5D=%21\*&f%5B%5D=&c%5B%5D=tracker&c%5B%5D=status&c%5B%5D=priority&c%5B%5D=cf_5&c%5B%5D=subject&c%5B%5D=author&c%5B%5D=assigned_to&c%5B%5D=cf_3&group_by=&t%5B%5D=)
## == Filing new issues ==
If you have problems with any of the tests, first search for a issue related to the same bug and add a comment on https://pulp.plan.io. Otherwise, report a bug to https://pulp.plan.io in the appropriate project section.
For example, you can find the issue for debian under the [Debain support](https://pulp.plan.io/projects/pulp_deb/) project.
Find all projects here: [Projects](https://pulp.plan.io/projects/)
## == How to report results ==