Project

Profile

Help

Test Day on August 8 2017 » History » Sprint/Milestone 40

Ichimonji10, 08/04/2017 05:14 PM

1 1 kdelee@redhat.com
# Test Day for 2.14 and pulp deb plugin
2
3 10 kdelee@redhat.com
## Join us on August 8, 2017 to test the 2.14 release and the new pulp_deb plugin!
4
5 1 kdelee@redhat.com
## Contents
6
7 12 kdelee@redhat.com
>   - How to join
8 36 kdelee@redhat.com
>   - How to contribute
9 4 kdelee@redhat.com
>   - Who is available for help
10 1 kdelee@redhat.com
>   - Prerequisites for test day
11
>   - Resources ( where to get RPMs, fedora images, etc)
12
>   - How to test
13
>   - Confirming existing issues
14
>   - Filing new issues
15
>   - How to report results
16
17
### Can't make the date?
18
19
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.
20
21
## How to join
22
23 39 kdelee@redhat.com
RSVP with this form to let us know you are coming and request help getting set up:  
24
https://goo.gl/forms/eHzCGsRDzDVWse923
25
26
If you don't get around to RSVPing, just show up!
27
28 1 kdelee@redhat.com
Join the [#pulp channel on freenode](http://irc.netsplit.de/channels/details.php?room=%23pulp&net=freenode)  
29
You can join via your favorite IRC client, or either of the two web clients below:
30
31
[pulp channel on irc2go](http://en.irc2go.com/webchat/?net=freenode&room=pulp)  
32 35 kdelee@redhat.com
[pulp channel on freenode webchat](http://webchat.freenode.net/?channels=%23pulp&uio=d4)
33 1 kdelee@redhat.com
34
Specify a nickname that you would like to go by, and keep it safe for work please!  
35
Many people choose something close to their name, as in Elijah's nickname is "elijah_d".
36
37 36 kdelee@redhat.com
## == How to contribute ==
38 1 kdelee@redhat.com
39
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)
40
41 37 kdelee@redhat.com
Things you can do:
42
43 38 kdelee@redhat.com
  - Collaborate with a Pulp QE member to provide a guide for installing on an cloud instance [ask in #pulp](http://webchat.freenode.net/?channels=%23pulp&uio=d4)
44 36 kdelee@redhat.com
  - walk through a [manual upgrade from an existing pulp install](http://docs.pulpproject.org/en/nightly/user-guide/release-notes/2.14.x.html#upgrade-instructions), 
45
  - installing manually both [pulp](http://docs.pulpproject.org/user-guide/installation/index.html) and the [pulp_debian plugin](https://github.com/pulp/pulp_deb/#installation) 
46 1 kdelee@redhat.com
  - Install using [ansible](https://pulp.plan.io/projects/pulp/wiki/Virtualization_quickstart#SETTING-UP-ANSIBLE-on-the-VM) and moving on to confirming functionality of the project, that bugs that were fixed in the release are indeed fixed, or other exploratory testing.
47 37 kdelee@redhat.com
  - Manually test user stories included in this release
48
  - Verify bug fixes in this release
49
  - Explore pulp functionality and provide feedback
50 1 kdelee@redhat.com
51
## == Who's available ==
52
53
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion.
54
55
### Quality Engineering
56
57 7 kdelee@redhat.com
  - Elijah DeLee (email: kdelee@redhat.com irc: elijah_d)
58
  - Preethi Thomas (email: pthomas@redhat.com irc: preethi) 
59
  - Kersom Oliveira (email: koliveir@redhat.com irc: kersom)
60 40 Ichimonji10
  - Jeremy Audet (email: jaudet@redhat.com irc: ichimonji10)
61 1 kdelee@redhat.com
62 6 kdelee@redhat.com
Specifically in the case of problem related to test day wiki, please reach out to Elijah DeLee at kdelee@redhat.com or on irc (nick: elijah_d)
63 1 kdelee@redhat.com
64 5 kdelee@redhat.com
## == Prerequisite for Test Day ==
65 1 kdelee@redhat.com
66 14 kdelee@redhat.com
  - Fedora 24, 25, or 26, RHEL 7, CentOS 7 system ( bare metal or VM )
67 1 kdelee@redhat.com
  - Root access on the system
68
69 15 kdelee@redhat.com
For a guide on some ways to spin up a VM on your machine. see [[Virtualization quickstart]]
70 1 kdelee@redhat.com
71 7 kdelee@redhat.com
## == Resources (where to get RPMs, fedora images, etc) ==
72 1 kdelee@redhat.com
73
The Pulp 2.14 beta repository is included in the pulp repo files:  
74
https://repos.fedorapeople.org/repos/pulp/pulp/fedora-pulp.repo for fedora 24 & 25  
75 4 kdelee@redhat.com
https://repos.fedorapeople.org/repos/pulp/pulp/rhel-pulp.repo for RHEL 7
76 1 kdelee@redhat.com
77 16 kdelee@redhat.com
You can also find the packages themselves here:  
78
https://repos.fedorapeople.org/pulp/pulp/beta/2.14/
79
80 4 kdelee@redhat.com
Fedora images:  
81 18 kdelee@redhat.com
You can find fedora "live" images here to install with:  
82 17 kdelee@redhat.com
[Fedora 25](http://mirrors.mit.edu/fedora/linux/releases/25/Workstation/x86_64/iso/)  
83
[Fedora 24](http://mirrors.mit.edu/fedora/linux/releases/24/Workstation/x86_64/iso/)  
84
[Fedora 26](http://mirrors.mit.edu/fedora/linux/releases/26/Workstation/x86_64/iso/)
85 1 kdelee@redhat.com
86 4 kdelee@redhat.com
## == How to test? ==
87 1 kdelee@redhat.com
88 7 kdelee@redhat.com
### == Run the tests ==  
89 9 kdelee@redhat.com
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.
90 1 kdelee@redhat.com
91 7 kdelee@redhat.com
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.
92 1 kdelee@redhat.com
93 7 kdelee@redhat.com
If you have trouble, email us or ping us on IRC and we can help you get it set up!
94
95
### == Exploratory testing ==
96
97 1 kdelee@redhat.com
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.  
98 24 kdelee@redhat.com
Get creative! Any problems you find please file a bug, or report to the IRC channel. See [Filing new issues](https://pulp.plan.io/projects/pulp/wiki/Test_Day_on_August_8\_2017#Filing-new-issues)
99 1 kdelee@redhat.com
100 22 kdelee@redhat.com
Find the 2.14 User Guide [here.](http://docs.pulpproject.org/en/2.14/nightly/user-guide/index.html)  
101 23 kdelee@redhat.com
Find the 2.14 RPM Quick Start Guide [here.](http://docs.pulpproject.org/en/2.14/nightly/plugins/pulp_rpm/user-guide/quick-start.html)
102 22 kdelee@redhat.com
103 23 kdelee@redhat.com
Look for other quick start guides among the plugin documentation. Note that the main docs.pulpproject.org may direct you to docs for 2.13, check the URL to make sure you are looking at the right version.
104 21 kdelee@redhat.com
105 8 kdelee@redhat.com
Think [CRUD](https://en.wikipedia.org/wiki/Create,\_read,\_update_and_delete)  
106
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?
107
108 25 kdelee@redhat.com
## == Verifying existing issues ==
109 1 kdelee@redhat.com
110 7 kdelee@redhat.com
There are three different ways you can use existing issues.
111
112 26 kdelee@redhat.com
### 1\. Verify that user stories marked "closed" work
113 7 kdelee@redhat.com
114 27 kdelee@redhat.com
You can find closed "user stories" [here](https://pulp.plan.io/issues?utf8=%E2%9C%93&set_filter=1&f%5B%5D=cf_4&op%5Bcf_4%5D=%3D&v%5Bcf_4%5D%5B%5D=2.14.0&f%5B%5D=tracker_id&op%5Btracker_id%5D=%3D&v%5Btracker_id%5D%5B%5D=3&f%5B%5D=&c%5B%5D=project&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&c%5B%5D=cf_4&group_by=project&t%5B%5D=)
115 7 kdelee@redhat.com
116 26 kdelee@redhat.com
### 2\. Verify that bugs fixed in the 2.14 release are indeed fixed!
117 7 kdelee@redhat.com
118 28 kdelee@redhat.com
[Bugs fixed in 2.14](https://pulp.plan.io/issues?c[]=tracker&c[]=status&c[]=priority&c[]=cf_5&c[]=subject&c[]=author&c[]=assigned_to&c[]=cf_3&f[]=cf_4&f[]=tracker_id&f[]=&group_by=&op[cf_4]=%3D&op[tracker_id]=%3D&set_filter=1&sort=priority%3Adesc%2Ccf_5%3Adesc%2Cid%3Adesc&utf8=%E2%9C%93&v[cf_4][]=2.14.0&v[tracker_id][]=1)
119 7 kdelee@redhat.com
120 29 kdelee@redhat.com
### 3\. Recreate outstanding bugs
121 7 kdelee@redhat.com
122 29 kdelee@redhat.com
Validate existence of [outstanding bugs.](https://pulp.plan.io/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=cf_8&op%5Bcf_8%5D=%3D&v%5Bcf_8%5D%5B%5D=2.14.0&v%5Bcf_8%5D%5B%5D=2.13.3&v%5Bcf_8%5D%5B%5D=2.13.2&v%5Bcf_8%5D%5B%5D=2.13.1&v%5Bcf_8%5D%5B%5D=2.13.0&v%5Bcf_8%5D%5B%5D=2.12.2&v%5Bcf_8%5D%5B%5D=2.12.1&v%5Bcf_8%5D%5B%5D=2.12.0&v%5Bcf_8%5D%5B%5D=2.11.1&v%5Bcf_8%5D%5B%5D=2.11.0&v%5Bcf_8%5D%5B%5D=2.10.3&v%5Bcf_8%5D%5B%5D=2.10.2&v%5Bcf_8%5D%5B%5D=2.10.1&v%5Bcf_8%5D%5B%5D=2.10.0&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=cf_8&t%5B%5D=)
123 7 kdelee@redhat.com
124 29 kdelee@redhat.com
If the bug is replicable and seems suitable for for pulp-smash tests, file an issue on [pulp-smash github issues](https://github.com/PulpQE/pulp-smash/issues)
125 7 kdelee@redhat.com
126 5 kdelee@redhat.com
## == Filing new issues ==
127 1 kdelee@redhat.com
128 30 kdelee@redhat.com
If you have problems with any of the tests, first search for a issue related to the same bug and add a comment on the issue at https://pulp.plan.io.
129
130
Otherwise, report the bug to https://pulp.plan.io in the appropriate project section.
131
132
For example, you can file a new bug or find an existing issue for the debian plugin under the [Debain issues](https://pulp.plan.io/projects/pulp_deb/issues?utf8=%E2%9C%93&set_filter=1&f%5B%5D=status_id&op%5Bstatus_id%5D=o&f%5B%5D=tracker_id&op%5Btracker_id%5D=%3D&v%5Btracker_id%5D%5B%5D=1&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=)
133
134
Again, if you are having trouble finding where to file your issue or search for existing ones, join us on IRC to get help!
135 1 kdelee@redhat.com
136 5 kdelee@redhat.com
## == How to report results ==
137 31 kdelee@redhat.com
138 32 kdelee@redhat.com
### New bugs
139 1 kdelee@redhat.com
140 32 kdelee@redhat.com
If you found a new bug, then you can file a new issue as described above. Also, refer to [[Issue filing template]]
141
142
### Verified bugs
143
144 33 kdelee@redhat.com
If you verified that a fix is correct or that a bug still exists, then comment on the issue with details about your system including all information pertinent to filing a new bug: [[Issue filing template]]
145
146
For more thoughts on what make a good bug report, see [here.](https://stackoverflow.com/help/mcve)