launchpad development|
Size: 2460
Comment:
|
Size: 166
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| These are my raw notes for some exploratory testing done on the Recipe feature. | List of Exploratory Testing reports for LP features |
| Line 3: | Line 3: |
| LEP: <https://dev.launchpad.net/LEP/SourcePackageRecipeBuilds> Bugs: <https://bugs.launchpad.net/launchpad/+bugs?field.tag=recipe> discoverability: https://qastaging.launchpad.net/bzr-pqm * there's no mention of recipes in the front page or the tour * Perhaps mention recipes somewhere in the tour? * when I'm logged out, on project page, there's no mention of recipes. Why? * from a project I own, I'd like to create a new recipe. nothing in overview project page saying anything about recipes * nothing in the code tab main page * not clear why I can't create a recipe for https://code.qastaging.launchpad.net/~launchpad-pqm/oops-tools/trunk? ownership issue? private branch? * https://code.launchpad.net/+daily-builds timed out for me https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1879C1296 * what's tarmac_recipe.setRecipeText api method? not documented in +apidoc * no way to list recipe through the api (bug 712329) * staging is offline and qastaging doesn't seem to process any recipes which makes things harder to test * private projects don't have a link to +new-recipe page in the trunk branch page but manually editing the url allows you to go to the page (e.g. https://code.launchpad.net/~launchpad-qa/qa-tagger/devel/+new-recipe) * some things I left intentionally unexeplored such as creating a new ppa for a recipe. * help text such the one shown in +new-recipe for syntax help doesn't have a scroll bar in chrome * error page for +new-recipe says There are 2 errors but only highlights one when I intentionally enter a "merge packaging lp:~matsubara/qa-tagger/packaging " directive when lp:~matsubara/qa-tagger/packaging doesn't exist in LP * Recipe may not refer to private branch: lp:~matsubara/qa-tagger/packaging error in +new-recipe in a private branch. although the link is not exposed it shouldn't work since it's a no-op, right? * recipe requested to be built daily takes some time to show up in the web ui as building which lead to people requesting a new build wasting build farm resources. The message shown is "This recipe has not been built yet." = still todo list = * workflow tests for the 3 different basic recipes * build from trunk as is * use trunk and merge another branch * use trunk and nest another branch * check error messages from emails when recipe fails to build |
* /RecipeFeature * /BugSubscriptionFeature * /UpstreamImportIntoUbuntu * /DerivingDistributionsFeature |
List of Exploratory Testing reports for LP features
