Pulp 2 14 Test Day Recap » History » Sprint/Milestone 1
pthomas@redhat.com, 08/09/2017 09:10 PM
1 | 1 | pthomas@redhat.com | # Pulp 2 14 Test Day Recap |
---|---|---|---|
2 | |||
3 | Test Day August 8/8/2017 |
||
4 | Build - 2.14 rc |
||
5 | |||
6 | Email announcements about the event were sent well in advance. We were able to get 3 participants from the community which is a big win from last year when we had 0 community participation |
||
7 | |||
8 | What went well: |
||
9 | |||
10 | We had 3 participants from the community (milkman, cixil & mxey). All of the participants had challenges with installing pulp on their test systems. This was in part due to pulp 2.14 not working on Fedora 26. We were not aware of the issue while writing the Test Day plan \[1\] and had announced it as one of the supported operating systems. Once identified the test day plan doc was updated. Pulp-QE was able to get everyone onboard quickly. So we able to engage the participants and continue testing. This was also a good exercise for Pulp-QE to get some testing done and verify fixed issues for Pulp 2.14 |
||
11 | |||
12 | I also want to give a shout out to Elijah- the pulp QE intern for taking ownership of the test day and making it a successful event. |
||
13 | |||
14 | The following issues were verified |
||
15 | |||
16 | https://pulp.plan.io/issues/2769 |
||
17 | https://pulp.plan.io/issues/2724 |
||
18 | https://pulp.plan.io/issues/2783 |
||
19 | |||
20 | The following issue was reproduced on 2.14 and updated |
||
21 | |||
22 | https://pulp.plan.io/issues/2346 |
||
23 | |||
24 | Following new Issues were filed. |
||
25 | |||
26 | https://pulp.plan.io/issues/2964 |
||
27 | https://pulp.plan.io/issues/2966 |
||
28 | https://pulp.plan.io/issues/2967 |
||
29 | |||
30 | What did not go well and suggestions for improvement:- |
||
31 | |||
32 | - Community participation and engagement |
||
33 | |||
34 | Explore ideas to attract more community participation. |
||
35 | |||
36 | - The onboarding experience could be better |
||
37 | |||
38 | Coming up with a better plan to get get test systems easily will help us to make use of the test day more effectively |
||
39 | |||
40 | Come up with a better plan to list what need to be tested |
||
41 | |||
42 | We had a broad list of how to participate |
||
43 | It may be more beneficial to come up with more detailed tasks and group them into sections. |
||
44 | |||
45 | \[1\] https://pulp.plan.io/projects/pulp/wiki/Test_Day_on_August_8_2017 |