Version 9 (modified by somayjain, 11 years ago) ( diff )


BluePrint: Quality Assurance


This blueprint outlines the development of the automatic testing framework. This automatic testing framework will provide robust testing of the code-base and ensure proper maintenance of the code.

Whenever some changes are added in the current code, it has to be validated and tested upon with the integration with the other components of the code. So, this framework will provide this support.

With tests running on a scheduler, continuous testing can be done. This is important to Sahana, seeing the rapid movement of the code-base. Currently, Sahana has automatic test framework, whose details can be found here


  • Developers - With an automatic testing framework setup, it will be relatively easier for the developers to test their changes in the code.
  • People who want to deploy Sahana - They would like to run the tests to ensure that the system is integrated well and ready for deployment.
  • Sahana as a service - Automated testing will provide Quality Assurance to it’s clients.

User Stories

  • Developers will run the test suite on making changes to the code to test if it works with the integration of the system. Developers may also see the test results mailed to the list to see the possible bugs introduced into the system.
  • People who want to deploy will run the test suite to check the functionality of the system.
  • The “bug marshalls” will review the test results mailed periodically by the CI Server and fix the bugs or log them.


<Group requirements in subsections, e.g. etc.> < requirements> <Identify different types of requirements:>


  • Maintain the CI Server to run the tests periodically and send the results.
  • Automatically Create Dummy Data while testing.
  • Extend Role Tests (Currently is limited to the IFRC roles for RMS)
  • Run Selenium and Smoke tests in multiple templates with multiple user accounts. Ideally, these tests can be run against each and every template where the target functionality is available. For templates where the functionality is not available, the test should auto-deactivate.
  • Clearer Error Messages in a way that anyone can reproduce them.
  • The CI Server should catch failures in any template. So, it should run tests across templates and include the template name in the aggregated report.
  • Simplify Selenium Tests and make them easier to read and more robust.
  • Load Tests




System Constraints



<Where relevant include alternative design options>

Data Model

(e.g. EER or class diagrams)


  • The CI Server runs the tests periodically and sends the results. On a regular basis, the bug marshalls review the test results and see if the reported negatives are false negatives or true negatives. If they are false negatives, they fix the tests. If they are true negatives, they report the bug on the trac or fix the bug themselves.
  • The developers make changes to the code and run the tests. If their changes do not break the tests, then this code is viable for merging.
  • The clients run the tests to make sure that the functionality this software is intended to provide is fulfilled.

Site Map

<for User Interface solutions>


<for User Interface solutions>



The seleium tests can be run on mainly IFRC template. WIth some changes, they can be run on the default template as well. However, they don’t work across templates.

The unit tests expect that some particular modules are enabled in the template. If they are not enabled and unit tests are run in that template, then false negatives are reported.

Current implementation of the selenium tests, smoke tests, role tests can be found here -

Unit tests and benchmark tests can be found here -


<Links to external resources>


Attachments (1)

Download all attachments as: .zip

Note: See TracWiki for help on using the wiki.