Custom Query (1174 matches)
Results (346 - 348 of 1174)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #371 | fixed | UTF-8 "ascii art" is broken (wrong encoding) | ||
| Description |
http://mediagoblin.com/u/aleksej/m/felichan-superjaron/ The text in the file is "Feli?an superjaron", but it appears as "Feliĉan superjaron!", both on its page and in the thumbnail (though the thumbnail is too small to see if "‰" is rendered). |
|||
| #372 | fixed | update copyright statements for 2012 | ||
| Description |
Pretty sure we need to go through and update the copyright statements for 2012. Also, while doing this pass, we should double-check that the FSF doesn't own the copyrights--they disclaimed them. Probably should assign copyrights on a file-by-file basis to whoever authored/edited them based on what git says. Putting this in the 0.2.1 target. I'll take it if no one else does by the weekend. |
|||
| #373 | fixed | Functional testing plan (test cases, e.g. for non-technical manual pre-release testing) | ||
| Description |
Some quotes from IRC: ======
<paroneayea> I think there's two things to that, we could use more unit tests, but we could also really use a functional testing plan
that is, a list of steps that somewhere before release time people can go through and test the software and make sure everything is working as expected
…
<paroneayea> we could probably use omgmg for it.
…
<AVRS> Mozilla uses Litmus, but it's going to be replaced.
…
<paroneayea> even just a wiki page detailing procedures would be good, but a better tool like Litmus or a replacement would be nice
<paroneayea> so this type of testing is less technical
it's more like you list a whole bunch of steps to test
like, submit a large image, see if it resizes right
register with a goofy username, see if it breaks
etc
make sure that all of the expected functionality works from a user-clicking-through perspective
Example of Litmus test results: https://litmus.mozilla.org/search_results.cgi?test_run_id=83 |
|||
