If you're new to Usenet, please read through the FAQs in
news.announce.newusers and hang out in news.newusers.questions for a
while before you consider posting.

If you do not know how to subscribe to comp.software.testing, you
first need to get Usenet access from an Internet service provider or
your company, and you need newsreader software.  Different service
providers support different newsreaders, so there is no general
answer.  Ask your service provider or local system administrator to
help.  If all else fails, use a web browser to access Usenet at
<http://groups.google.com/groups
?hl=en&lr=&safe=off&group=comp.software.testing>.

The original charter for comp.software.testing can be found at
<http://tsunami.jpl.nasa.gov/TEL/docs/cst-charter.html>.  Here's an
excerpt (with corrections):

    CONTENTS:

    For the purpose of this discussion, we will assume that a system is
    composed of hardware, software, people, and procedures. The
    proposed group should be chartered to include discussions
    characterized by the following list of subjects, compiled from
    preliminary discussions:

        system test automation
        system test planning
        system test optimization (e.g. minimize regression testing)
        test tools
        test metrics
        measurement technology
        nature of testing under various development models
            (e.g. object-oriented, real time, etc...)
        testing in a rapid prototyping environment (i.e. sans spec)
        relationship of various classes/types of tests to requirements, ...
        conference and symposium announcements
        the definition of "software testing" and its relationship to
            SQA and debugging.
        requirements traceability
        risk-based testing
        the most useful form of specifications and functional
            requirements from the tester's point of view.
        testing techniques, e.g., structured testing using control
            flowgraphs and basis path testing, equivalence class
            partitioning, boundary value analysis, cause-effect graphing,
            path predicate testing, data flow testing, program slices,
            data object state and usage analysis, data flow anomaly
            analysis, and sensitivity analysis.
         test coverage criteria, e.g., statement (C0), path, branch (C1),
            module (S0), and call-pair (S1) coverage criteria.

    All levels of testing for both hardware and software should be
    considered appropriate subject matter. While it is likely that the
    group will take on a software flavor early on, we should try to
    generate interest and input from people with hardware and system
    testing experience and perspective. It is especially important that
    we foster discussion of *system* level testing issues, since this
    is the weakest area of our collective knowledge.