Difference between revisions of "Unified Testing"

OurWork

What (summary)

To have a single testing engine that tests code for PHP, compost and javascript code.

Why this is important

Until now, we use rake test to test our compost code but we don't have any such framework for testing the PHP and javascript code. This does not let us write bug free php and javascript code, and don't let us refactor our code often. This testing framework would let us do exactly that.

DoneDone

• proper permissions are required to be able to execute any of the au_web_services (logged-in sysop for our stuff)
• au_web_services shows links to the main functional tasks that we perform (test, patrol, crm)
• au_web_services/test is a web service that shows links to all the test suites you can run
• au_web_services/test/XXX runs all the tests in the suite XXX and reports the results in a friendly manner
  • au_web_services/test/ruby
  • au_web_services/test/javascript
  • au_web_services/test/php
  • au_web_services/test/all executes all tests (javascript, php, and ruby) at all levels of abstraction (unit, functional, integration) reports the results in a friendly manner

Steps to get to DoneDone

• Make au_web_services/test/ruby run all of our ruby tests and report the results in a friendly manner
• Make php_run_tests work for our live branch that tests all the test cases inside live directory.
• Report results as they come in (incrementally) rather than batching them and then reporting the results
• Add test/javascript.html that tests all the tests for javascript code.