Test Day on August 8 2017 » History » Revision 33

Revision 32 (, 07/26/2017 06:26 PM) → Revision 33/52 (, 07/26/2017 06:28 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! 

 ## Contents 

 >     - 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, and report your results as detailed in "How to report results" section below. 

 ## How to join 

 Join the [#pulp channel on freenode](   
 You can join via your favorite IRC client, or either of the two web clients below: 

 [pulp channel on irc2go](   
 [freenode webchat]( (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]( and the new [pulp debian plugin]( 

 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: irc: elijah_d) 
   - Preethi Thomas (email: irc: preethi)  
   - Kersom Oliveira (email: irc: kersom) 
   - Jeremy Audet (email: irc: Ichimonji10) 

 Specifically in the case of problem related to test day wiki, please reach out to Elijah DeLee at or on irc (nick: elijah_d) 

 ## == Prerequisite for Test Day == 

   - Fedora 24, 25, or 26, RHEL 7, CentOS 7 system ( bare metal or VM ) 
   - Root access on the system 

 For a guide on some ways to spin up a VM on your machine. see [[Virtualization quickstart]] 

 ## == Resources (where to get RPMs, fedora images, etc) == 

 The Pulp 2.14 beta repository is included in the pulp repo files: for fedora 24 & 25 for RHEL 7 

 You can also find the packages themselves here: 

 Fedora images:   
 You can find fedora "live" images here to install with:   
 [Fedora 25](   
 [Fedora 24](   
 [Fedora 26]( 

 ## == How to test? == 

 ### == Run the tests ==   
 If you'd like to run the integration test suite, [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 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. See [Filing new issues](\_2017#Filing-new-issues) 

 Find the 2.14 User Guide [here.](   
 Find the 2.14 RPM Quick Start Guide [here.]( 

 Look for other quick start guides among the plugin documentation. Note that the main may direct you to docs for 2.13, check the URL to make sure you are looking at the right version. 

 Think [CRUD](,\_read,\_update_and_delete)   
 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? 

 ## == Verifying existing issues == 

 There are three different ways you can use existing issues. 

 ### 1\. Verify that user stories marked "closed" work 

 You can find closed "user stories" [here]( 

 ### 2\. Verify that bugs fixed in the 2.14 release are indeed fixed! 

 [Bugs fixed in 2.14]([]=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) 

 ### 3\. Recreate outstanding bugs 

 Validate existence of [outstanding bugs.](\*&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=) 

 If the bug is replicable and seems suitable for for pulp-smash tests, file an issue on [pulp-smash github issues]( 

 ## == 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 the issue at 

 Otherwise, report the bug to in the appropriate project section. 

 For example, you can file a new bug or find an existing issue for the debian plugin under the [Debain issues]( 

 Again, if you are having trouble finding where to file your issue or search for existing ones, join us on IRC to get help! 

 ## == How to report results == 

 ### New bugs 

 If you found a new bug, then you can file a new issue as described above. Also, refer to [[Issue filing template]] 

 ### Verified bugs 

 If you verified that a fix is correct or that a bug still exists, correct, then comment on the issue with details about your system including all information pertinent to filing a new bug: [[Issue filing template]] 

 For more thoughts on what make a good bug report, see [here.](