Last modified: 2013-03-16 22:23:23 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T40964, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 38964 - Refactor page translation code
Refactor page translation code
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
Translate (Other open bugs)
master
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-08-02 12:06 UTC by Niklas Laxström
Modified: 2013-03-16 22:23 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Niklas Laxström 2012-08-02 12:06:08 UTC
Currently it is very hard to write tests for page translation, because the code is in Special:PageTranslation.
Comment 1 Siebrand Mazeland 2013-03-04 19:34:48 UTC
Could you elaborate a bit on what you would like to get done here? That would allow someone else to take a stab at it, possibly :).
Comment 2 Niklas Laxström 2013-03-04 20:26:57 UTC
I would like to have unit or integration tests for the basic page translation actions:
* discourage a page
* encourage a page
* mark new page for translation
* remark existing page for translation
* unmark page from translation
* remove translatable/translation page
* move translatable/translation page
Comment 3 Chris McMahon 2013-03-04 20:28:19 UTC
This might be worth doing as browser-level tests, but I'm not sure.
Comment 4 Siebrand Mazeland 2013-03-04 21:07:02 UTC
(In reply to comment #3)
> browser-level tests

This is surely something that could be a 3rd priority for browser level tests in LangEng, but then they would mostly only exist to avoid having to unit test. Not sure if that's a correct trade off. But hey, if you'll have Chris, I'll try to get it in ;).

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links