gecko-dev/webtools/litmus
zach%zachlipton.com 7d04f23f2a * Add additional json hooks to retrieve lists of products, platforms, etc...
* (bug 334871) Search test lists by product/testgroup/subgroup
* Allow printing of all testcases matching a query
* Improve wording and organization of links in options sidebar
2006-07-28 22:26:43 +00:00
..
Litmus - removing duplicate scpoing from cut-n-paste 2006-07-22 01:24:20 +00:00
css * Add additional json hooks to retrieve lists of products, platforms, etc... 2006-07-28 22:26:43 +00:00
images b=335382 2006-05-01 21:42:54 +00:00
js b=345272 2006-07-22 01:18:48 +00:00
skins Actually display the correct stats in stats.cgi. Also move the footer down a little. 2005-08-17 23:35:30 +00:00
t Fix for bug 315479 part 2: Cross-site scripting security holes in templates. All tests now pass. 2005-11-15 17:30:57 +00:00
templates/en/default * Add additional json hooks to retrieve lists of products, platforms, etc... 2006-07-28 22:26:43 +00:00
testcase_files - adding apache access directives for new testcase_files directory tree 2006-06-07 22:55:50 +00:00
testrunner_migration - adding script used to generate testday stats 2006-07-18 16:41:30 +00:00
.cvsignore Add data/ to cvsignore and create the data directory at install-time. 2005-09-07 00:43:37 +00:00
.htaccess
INSTALL -Web Services: support a web services interface for test result submission. See http://wiki.mozilla.org/Litmus:Web_Services for details. 2006-06-22 23:21:38 +00:00
Litmus.pm b=314928 2006-01-25 17:03:40 +00:00
Makefile Add 'make cache' target. 2006-03-21 00:38:56 +00:00
README
advanced_search.cgi - remove errant comment 2006-06-27 15:58:37 +00:00
common_results.cgi b=314928 2006-01-25 17:03:40 +00:00
edit_users.cgi Change some form field names to silence password manager. 2006-06-16 18:54:37 +00:00
enter_test.cgi Fix enter_test.cgi so it sets the author, creation_date, and version fields of new testcases. 2006-06-20 17:41:53 +00:00
favicon.ico - new look-and-feel code, css into css/ directory; 2005-10-11 18:44:16 +00:00
index.cgi Manage testgroup 2006-06-27 15:51:58 +00:00
json.cgi * Add additional json hooks to retrieve lists of products, platforms, etc... 2006-07-28 22:26:43 +00:00
login.cgi - add login link to sidebar 2006-02-24 23:37:02 +00:00
logout.cgi b=314928 2006-01-25 17:03:40 +00:00
manage_categories.cgi - renamed edit_categories.cgi to manage_categories.cgi for consistency's sake 2006-07-14 17:47:33 +00:00
manage_subgroups.cgi Bug 343007 - filter lists in management interfaces. Patch adds AJAX filter options to manage_*.cgi pages and exposes an interface for scripts to request a list of test ids, subgroup ids, testgroup ids, matching a given criteria. 2006-07-13 17:17:59 +00:00
manage_testcases.cgi Bug 343007 - filter lists in management interfaces. Patch adds AJAX filter options to manage_*.cgi pages and exposes an interface for scripts to request a list of test ids, subgroup ids, testgroup ids, matching a given criteria. 2006-07-13 17:17:59 +00:00
manage_testgroups.cgi b=345272 2006-07-22 01:18:48 +00:00
populatedb.pl - Add is_automated_result flag to test_results table to track when results are part of automated testing scripts. 2006-06-27 00:39:09 +00:00
populatedb.sql Remove ENUM cols from populatedb.sql to match schema. 2006-01-17 04:43:56 +00:00
preview.cgi - added table related_testcases to track cloned testcase relations 2006-06-20 19:34:53 +00:00
process_test.cgi - update reference to process_test.cgi 2006-06-23 15:35:30 +00:00
robots.txt Add coop's robots.txt file from the production install 2006-06-13 19:25:45 +00:00
run_tests.cgi - adding script to parse testcases from submitted XML (add_testcases_from_xml.pl) 2006-07-12 15:01:08 +00:00
runtests.pl Let's actually pass the tests...Removing tabs from a couple of files (replacing them with spaces) and fixing the test scripts to work properly. 2005-11-10 23:24:46 +00:00
schema.pl b=345272 2006-07-22 01:18:48 +00:00
search_results.cgi - remove errant comment 2006-06-27 15:58:37 +00:00
show_test.cgi * Add additional json hooks to retrieve lists of products, platforms, etc... 2006-07-28 22:26:43 +00:00
simpletest.cgi b=323768 2006-06-05 04:07:29 +00:00
single_result.cgi - remove errant comment 2006-06-27 15:58:37 +00:00
stats.cgi b=323768 2006-06-05 04:07:29 +00:00
testlist.cgi b=323768 2006-06-05 04:07:29 +00:00

README

===Litmus===

If you're reading this, you've downloaded, received, or simply conjured
out of thin air, a copy of the Litmus testcase management system.
Presumably, you're reading this file because you have some sort of
question about Litmus. Hopefully, if we've done our job right, this file
ought to answer your questions. 

Q: What is Litmus?
A: Litmus is a testcase management system. Its goal is to allow users to
enter software tests, run them, and view and manage the results. Along
the way, users can expect to be able to do queries and reports and have
access all the usual features they expect from a first-class web
application. The reality may be somewhat different than this goal.
Litmus is developed by mozilla.org.  

Q: How do I install this dang thing?
A: You probably want the file called INSTALL.

Q: Where is the real documentation?
A: Hahahaha. What is this "documentation" you speak of? You might want
to check out the Litmus Wiki, which may or may not contain useful
information. See http://wiki.mozilla.org/Litmus.

Q: What needs to be done?
A: See http://wiki.mozilla.org/Litmus:Todo

Q: How much does it cost?
A: Nothing. Litmus is Free Software, licensed under the Mozilla Public
License.

Q: Wait. Isn't "testcase" two words? 
A: Not here it isn't. 

Q: Waaaaaaah. Why is Litmus written in Perl and not
PHP/Python/Java/Objective Pascal/Latin?
A: Because I know Perl. Duh. Also because Litmus uses some code from
Bugzilla, and it wouldn't be able to do this if it was written in some
other language. Camels are also some of the least buggy animals around,
as they swat flies away with their tails. 

Q: I'm still confused. You didn't answer my question. I don't know what
to do. Help!
A: First of all, that's not a question. In any case, your best bet is
probably to email Zach Lipton <zach@zachlipton.com>, and if you ask
nicely and don't make too much of a pest of yourself, he'd be glad to
get you on the right track.