gecko-dev/webtools/litmus
2006-04-06 19:39:35 +00:00
..
css b=321120 2006-02-13 23:10:42 +00:00
images b=321120 2006-02-13 23:10:42 +00:00
js - use the right object type <sigh> 2006-02-23 23:02:28 +00:00
Litmus Only load Litmus::BugzillaDBI if Bugzilla auth is enabled, otherwise we get errors when the database connection fails. 2006-04-06 03:29:37 +00:00
skins
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 - default to en-US 2006-03-06 19:58:18 +00:00
testrunner_migration - allow --force updating of testcases 2006-04-06 19:39:35 +00:00
.cvsignore
.htaccess
advanced_search.cgi b=314928 2006-01-25 17:03:40 +00:00
common_results.cgi b=314928 2006-01-25 17:03:40 +00:00
edit_categories.cgi b=314928 2006-01-25 17:03:40 +00:00
favicon.ico
index.cgi b=314928 2006-01-25 17:03:40 +00:00
INSTALL
Litmus.pm b=314928 2006-01-25 17:03:40 +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
Makefile Add 'make cache' target. 2006-03-21 00:38:56 +00:00
populatedb.pl Only load Litmus::BugzillaDBI if Bugzilla auth is enabled, otherwise we get errors when the database connection fails. 2006-04-06 03:29:37 +00:00
populatedb.sql Remove ENUM cols from populatedb.sql to match schema. 2006-01-17 04:43:56 +00:00
process_test.cgi b=320423 2006-02-07 18:20:53 +00:00
README
run_tests.cgi - standardize on 'enabled' as field name of choice for entities that can be toggled on or off 2006-02-24 22:02:41 +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 - standardize on 'enabled' as field name of choice for entities that can be toggled on or off 2006-02-24 22:02:41 +00:00
search_results.cgi b=314928 2006-01-25 17:03:40 +00:00
show_test.cgi - fine-tune the rules for display (enabled + community_enabled) 2006-04-06 19:37:39 +00:00
simpletest.cgi - standardize on 'enabled' as field name of choice for entities that can be toggled on or off 2006-02-24 22:02:41 +00:00
single_result.cgi b=320423 2006-02-07 18:20:53 +00:00
stats.cgi b=314928 2006-01-25 17:03:40 +00:00
testlist.cgi b=314928 2006-01-25 17:03:40 +00:00

===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.