Audience: All community members–newcomers, aspiring core contributors, and current core contributors. No technical expertise necessary
The Aximprovements team (@farhankhan , @Irtaza_Akram and @Salman_Nawaz ) has been hard at work cleaning up the code behind our core learning components, including two very critical ones, the Problem component and Video component. (If you’re curious, here are the technical details).
Now, we are seeking volunteers who would be willing to help manually test those two cleaned-up components for regressions.
We’ll provide a sandbox environment running Studio and Courseware where the code cleanups (the “extracted XBlocks”, in technical terms) are enabled.
We’ll use the Problem and Video guides in the educators docs as a basis for test instructions. We’ll also draw from some of the relevant Ulmo release test cases.
If you’re an expert in Open edX Problem and Videos, great. If not, no problem–we’ll help you get up to speed, and you’ll be an expert by the end.
We’ll be manually testing too–but the more eyes we have, the better! We’ll use a shared document to collaborate on test progress and share results.
If you’d like to help, just comment here or DM me on Slack and we can get you started!
Definitely! Regular work has been eating all my time in the past few months and I haven’t had time to update it for (looks at notes) Teak yet, but it should have a large number of problem test items.
I also have Grape Ape, our internal test course made of nonsense and glitter. I can probably trim down a copy of it to just things that should work. Happy to give you access too if you don’t already have it.
One thing we’ve been unable to test manually is the uploaded video workflows, as they are mostly undocumented and (as far as we know) only used by 2U currently. I’m working with Devasia from AppHelix to see if we can test that at all, but I don’t think we need to block the rollout of the refactoring on that.