gecko-dev/webtools/litmus
ccooper%deadsquid.com e7c7b2a6e5 -removing access control file 2006-11-29 17:27:50 +00:00
..
Litmus - preferentially sort subgroup and testcase lists by name to make it easier for admins to find what they're looking for 2006-11-28 23:28:33 +00:00
css b=358035 2006-11-01 22:13:32 +00:00
images b=358035 2006-11-01 22:13:32 +00:00
js b=355548 2006-11-14 20:23:31 +00:00
migration - add access control 2006-11-29 17:27:04 +00:00
skins
t
templates/en/default - fix editing of testgroups 2006-11-17 01:25:15 +00:00
testcase_files
.cvsignore
.htaccess
INSTALL - suggested additions to INSTALL docs and scripts from donovan@catalyst.net.nz 2006-10-18 13:05:14 +00:00
Litmus.pm
Makefile
README
advanced_search.cgi
aggregate_results.cgi b=351741 2006-09-13 17:45:50 +00:00
common_results.cgi
edit_users.cgi b=328489 2006-08-29 17:49:14 +00:00
enter_test.cgi b=358035 2006-11-01 22:13:32 +00:00
favicon.ico - updated favicon for Litmus 2006-08-03 16:43:53 +00:00
index.cgi
json.cgi b=358035 2006-11-01 22:13:32 +00:00
login.cgi Automatically redirect to index.cgi if the user is already logged in and loads login.cgi rather then giving an error. 2006-08-03 23:51:01 +00:00
logout.cgi
manage_categories.cgi b=358035 2006-11-01 22:13:32 +00:00
manage_subgroups.cgi - preferentially sort subgroup and testcase lists by name to make it easier for admins to find what they're looking for 2006-11-28 23:28:33 +00:00
manage_testcases.cgi - preferentially sort subgroup and testcase lists by name to make it easier for admins to find what they're looking for 2006-11-28 23:28:33 +00:00
manage_testgroups.cgi b=328489 2006-08-29 17:49:14 +00:00
populatedb.pl b=360954 2006-11-16 21:48:50 +00:00
populatedb.sql
preview.cgi
process_test.cgi
robots.txt - add missing slash 2006-08-03 14:25:06 +00:00
run_tests.cgi - don't override success/failure/info messages with loading messages 2006-08-04 16:33:14 +00:00
runtests.pl
schema.pl b=360954 2006-11-16 21:48:50 +00:00
search_results.cgi - allow searching for results with comments attached 2006-11-03 17:23:28 +00:00
show_test.cgi - fix check for testcase ID 2006-11-14 21:32:07 +00:00
simpletest.cgi
single_result.cgi b=343919 2006-09-06 17:34:39 +00:00
stats.cgi
testday_report.cgi b=358035 2006-11-01 22:13:32 +00:00
testlist.cgi

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.