FOR ARCHIVAL PURPOSES ONLY

The information in this wiki hasn't been maintained for a good while. Some of the projects described have since been deprecated.

In particular, the "Ushahidi Platform v3.x" section contains information that is often misleading. Many details about this version of Platform have changed since.

This website is an extraction of the original Ushahidi wiki into a static form. Because of that, functions like logging in, commenting or searching will not work.

For more documentation, please refer to https://docs.ushahidi.com

Skip to end of metadata
Go to start of metadata

Welcome!

Welcome to the home of QA on the Ushahidi Platform (version 3.0)!

The main purpose of software quality assurance is to provide adequate confidence that the software conforms to established technical requirements through a planned and systematic pattern of actions. Software quality assurance confirms the following:

  1. Products are developed according to defined standards
  2. Plans are defined within the defined standards
  3. Procedures are performed according to plans

Through a variety of approaches such as automated testing, exploratory testing, manual testing, user testing and functional testing, Ushahidi aims to ensure high quality and defect free products.

Get Involved

We'd love to have your help in testing our products, and especially Ushahidi version 3.0! Here's how:

  • Have a look at our demo sites quick guide to get familiar with the website.
  • Download and install the platform on your computer or server. Instructions on how to set up an instance can be found on this wiki.
  • Have a look at the automated tests structure and how you can create your own tests. You can also try running the already implemented tests.
  • Once you have access to the demos sites, jump in and do some manual testing. No prior experience is needed for this!

Found a bug?

We appreciate and welcome any feedback we can get from you. If you find a bug while testing our product, please let us know by adding an issue on our bug tracking tool, Phabricator. We shall respond to the issue as quickly as we can. It is important to write clear and effective bug reports so that they can fixed faster. Please follow this guide when writing bug reports.

 

 

 

  • No labels