Showing posts with label Testing. Show all posts
Showing posts with label Testing. Show all posts

Thursday, August 29, 2013

Reviving my bot for #Wikidata IV

An appropriate response of a fixed bug is .. more testing. The harvest_template.py did get a bug fixed so testing the latest and greatest was in order. The bug has been fixed. I am grateful so it was time to do run attempt to import more data from Wikipedia and do some more testing at the same time.

At this time I am importing political party information from templates of obvious politicians; people who are for instance in a category like "Presidents of Argentina". I found new bugs..
  • When there is no party indicated, the bot aborts
  • When the party is a "red link", the bot aborts
  • When there are multiple parties indicated, it only adds the first one
I also found that there are Wikipedia articles without a Wikidata entry, they are ignored. 

I am really happy with the help I get in running the pywikipedia software. It becomes however obvious that importing data from Wikipedia into Wikidata in this way is not mature.
Thanks,
       GerardM

PS I imported some 400+ records while testing :)

Tuesday, March 13, 2012

#multilingweb - #i18N and #l10n testing framework

A subject for the conference about the Multilingual Web is what gaps exist in supporting a multilingual web. Obviously people who are living the multilingual web like my colleagues in the WMF localisation team suffer these gaps. Our team has been asked what to do next and one idea of Amir I love to put forward.
A testing framework for localization
I searched and I couldn't find any testing framework that is focused on localization. Many localization-specific issues must be tested, for example, grammatical correctness of generated messages, text readability in different scripts, support for encodings and fonts, etc. You can find a fuller list in Wikipedia (i wrote most of that section myself). It is possible to test all these things using the current frameworks, but much of it would be manual.
For example, i'm not familiar with any tool that would automatically or semi-automatically create screenshots of all the possible translated strings with their complete context. This would be useful for the translator, to see how to translate a message; for the developer, to see whether any message runs out of the screen or hides a button that must remain visible; and for the tester who speaks the language and wants to see whether all the generated messages are grammatically correct. Currently, a developer must do this manually;
it is time-consuming, inefficient, hard to plan and to maintain, and the fact is that the developers are hardly ever doing this.
Such a testing framework would be really great for so many organisations. At translatewiki.net we support many organisations with their internationalisation and localisation. A framework will make it easy to repeat the testing often. This will improve consistency and quality and makes for a great multi lingual experience.
Thanks,
     GerardM

Friday, January 20, 2012

#Testing, 123, testing, testing

Testing #MediaWiki is fun. There are many, many Wikis and they are all different. Yes, we can create tests for a plain vanilla WMF Wiki. In reality they are all different. They are different because most have their specific modifications, their own gadgets. All have the potential to fail what passed the integration tests for plain vanilla wikis.

To known this, you have to have tests in the first place and the WMF Localication team is getting to grips with the testing platforms and building the tests that enable continuous integration.

Building tests is fun. You start with software that seems to be working perfectly and the tests prove that it has issues. This may sound odd, because it is not as if the software was not tested. A test that can be automated is validated in different ways. When a browser shows characters only a little bit different when comparing output, an automated test will catch this when it compares it to what is defined as correct. In many ways, automated tests test on a lower level then what humans do.

It is just that we do not have the humans to test over and over again.
Thanks,
     GerardM

Wednesday, December 14, 2011

Testing the #MediaWiki visual editor ... with #Russian

When you follow MediaWiki development, you will be eager to test the visual editor. A very alpha version of the software is available for testing and, at this time it allows you to enter a text in the Latin script.

That is to say; Amir found a way to enter text in Russian. He uses the Mozilla transliterator. He types Latin characters and Firefox transliterates it into Cyrillic. For Amir the transliterator is a must have feature.
Without it i couldn't write an email to my sisters, comment on Russian blogs or write in the Russian Wikipedia. (You can quote me)
I am happy to quote him and share with you how he sneakily tests the visual editor in Russian anyway. As you can see many more languages are supported in this way.

Yes, your bug reports are eagerly awaited ...
Thanks,
       GerardM

Wednesday, August 03, 2011

Want to test the PHP mobile #Wikipedia environment ?

At #Wikimania you learn things that may have been there for some time. One such is the invitation at the bottom of every Wikipedia to its mobile view. What you get is the mobile software as developed in PHP.

This is really nice because this mobile view is integrated in MediaWiki itself and consequently new functionality may affect the mobile view. Currently the functionality is the same as what is available in Ruby. There is a need for people to test the new mobile functionality so please check it out.

When you do not have a necessary font, you will see the little boxes indicating Unicode characters like in the illustration below.


At this stage, the mobile developers need all the feedback they can get. Try it on your computer, your mobile... Compare it to the Ruby version that can be found at **.m.wikipedia.org. Let us know where the new software lets you down compared to the old.

Once the new software is as good as the old, we can move on and bring in new functionality that helps you to get the most out of your mobile. Things like uploading pictures directly from your phone into Commons would be nice...
Thanks,
      GerardM

Thursday, March 10, 2011

Test #offline #Wikipedia on your #Android or #iPhone

#Okawix is completing its functionality for the best selling smart phones. Now they need people to test it for them so that they can pick off all the bugs.

Testing and localising the Okawix software are the perfect preparation for the next phase of its development, the support for openZIM. The realisation of this next phase will surely make the Wikimedia Foundation really happy because it will finally provide them with an application that supports Wikipedia content in the openZIM format with a user interface in the same language.
Thanks,
      GerardM

Friday, November 05, 2010

How well does #MediaWiki support right to left languages ?

I read the following conversation on IRC:

[19:50]AryehGregor  Have we looked at this? http://code.google.com/p/bidichecker/
[19:53]Nikerabbitwhy should we? we already know bidi is broken
[20:16]AryehGregor. . .
[20:17]Nikerabbitit's not funny, it's sad

The reaction of Nikerabbit, an expert on language support is surprising me. Recognisable improvements came to MediaWiki with the work done for the Usability Initiative. As many of our bigger Wikipedias are using scripts that are right to left, it is crucial to implement this properly. Having a tool for the testing of bidirectional functionality, a tool that prevents regressions makes excellent sense.

I am left with two questions:
  • what is the state of BIDI support
  • does it make sense to make the BidiChecker part of the testing environment.
Thanks,
      GerardM

Friday, September 04, 2009

Supporting MediaWiki extensions

Translatewiki.net supports MediaWiki and its extensions. There are many extensions actively used and some extensions may not be used at all. We do not really know. What we do know is that some have not been updated for a long time.

The PovWatch extension for instance has not been updated since June 2006 and, it is not clear if this functionality works at all and if so for what releases of MediaWiki. It may be that this extension has never been used. It is not clear that they they have been tested for their functionality.. All this makes extensions like this problematic for Wiki administrators and users alike.

There may be more extensions that are not used but are localised at translatewiki.net. Removing such extensions prevents our localisers from wasting their time.

You can help us by identifying the extensions that are no longer relevant.
Thanks,
GerardM

Wednesday, August 26, 2009

Database configuration

The thing about a hackaton is that people come together and discuss needed functionality and often make big strides in making things happen. One thing that is taking shape is the "configuration database". As I understand it, it is based on the Configure extension and is extended so that it has all the functionality needed by the Wikimedia Foundation.

The things that excites me is that when more functionality actually makes use of a database of configurations, it will become possible to actually use different configurations when testing. As it is, the MediaWiki Testing Environment is at this moment very much about setting up an environment ready for testing. With configurations available in a database it is possible to test using these configurations. This makes for even more flexible testing.
Thanks,
      GerardM

Thursday, May 28, 2009

Requests to implement the Babel extension

The Babel extension is one of my favourites. There are several reasons why:
  • it is implemented and supported at translatedwiki.net
  • there are many localisations for the messages involved
  • when you install it, all the localisations are instantly available
  • it is an extension 
  • it is not based on templates
The good news is that many people appreciate Babel for what it is. There are several Wikipedias who have requested for this extension to be implemented.  They are even considering to put this extension to the vote for the German Wikipedia..

There is one problem; the code needs to be assessed. It already has the endorsement of all the developers at translatewiki.net...
Thanks,
      GerardM

Sunday, March 15, 2009

Appreciating Semantic MediaWiki

I am spending a considerable amount of time working on the "Wikiation Extension Testing Environment" (WETE). This is software that is designed to test MediaWiki and its extensions in many configurations. Wikiation is a Dutch company that provides hosting and value added services in the Dutch language and with MediaWik as its platform. It is of extreme importance for Wikiation that the software just works. The customers of Wikiation rely on a quality service, they expect that the systems are running.

One of the customers of Wikiation is interested in Semantic MediaWiki. Installing SMW is complicated, there are many extensions, these extensions have their prerequisites and it is easy to get it wrong. All of SMW is under constant development and consequently the latest is not necessarily the greatest.

As I am working together with Wikiation to develop WETE, SMW is an obvious target to test. I blogged about the lessons learned and several people got into contact with me. I learned that SMW is used for a wide variety of topics, it is used for genomics and for chicks, it is used for contact information and for a science fiction MMO... There is even a hosting company who specialises in SMW.

What SMW helped me to appreciate even more is the great number of people and organisations that have their MediaWiki installation. SMW is great software and it deserves the best support. I am happy that WETE is starting to play a part in this.
Thanks,
      GerardM

Wednesday, January 14, 2009

Usability - Semantic Forms at Chickipedia

A friend of mine had me look at Chickipedia. I must say that I was impressed with the way MediaWiki was made to look good.. In this website they use Semantic MediaWiki and Semantic forms. I am impressed because it hides a lot of hard stuff from the users.


It looks as good as the Wikia info boxes. What I would welcome are demonstration wikis where all the competing approaches to usability can be shown. When we test the extensions, when we ensure great documentation, we can package all these approaches so that all organisations can make up their mind of the state of the MediaWiki opportunities.
Thanks,
       GerardM

Saturday, November 22, 2008

Improving the MediaWiki usability

Eighty percent of the Wikimedia Foundation projects are not doing well. They hardly grow both in size and in community and there is room for quality improvement. Given that all our projects are done by volunteers and given that we rely on growing our community in order to improve our projects usability is key. It has to be easy and inviting to collaborate.

UNICEF hosts several MediaWiki wikis. They found that people have a problem contributing. They did usability studies in Tanzania and found that 100% of their test subjects were not able to create a new article. This is shocking. It helps explain why our projects have a problem. Usability and localisation are the key enablers for people to participate.


As part of the Extensions Testing project, we are testing the UNICEF extensions. The CreatePage extension now works. The picture above shows the default look with the Monobook skin. The first thing we can do is include a link to "Create article" in the sidebar.


For the Uniwiki, a different skin has been developed and a "Create Page" button is given a lot of prominence. Another innovation is the idea of using templates for certain types of articles. This became feasible as a consequence of the "Create Page" functionality.

It already makes sense for the WMF to implement this one extension as it is likely to make a big difference. Consider, 100% of the test subjects in Tanzania proved to be unable to collaborate so we desperately need to do better. We can start by first implementing the core functionality; a link in the sidebar and a special page. As we gain experience, we can put more polish on it. We can work on visibility, we can create our own templates, we can work on the skin.

We can make a start improving our usability. Given the state of the majority of our projects, it is easy to argue why.
Thanks,
GerardM