ES5conform Wiki & Documentation Rss Feed

Updated Wiki: Home

dfugate — Mon, 08 Aug 2011 17:57:03 GMT

A New Home for ES5Conform

The goal of the ES5Conform CodePlex project was to build a suite of tests for new features added in the 5th edition of the ECMAScript language specification. As this test suite matured, it became desirable to extend it with tests for features added in earlier versions of the ECMAScript standard that are still present in the 5th edition today. A comprehensive test suite for the 5th edition in its entirety is extremely useful for JavaScript implementers.

To achieve this goal, the tests from ES5Conform (which were focused on ECMAScript 5) have been contributed along with Google’s Sputnik tests (focused on ECMAScript 3) to Test262, a test suite supported by the ECMAScript committee. To this end, all active development on ES5Conform has been migrated to test262 and test defects are now tracked on http://bugs.ecmascript.org. Other improvements were made in the transition to test262, and the best example of this is that the entire test suite is conveniently runnable directly from the test262 website. Also worth pointing out is that development of test262 is now an actual project of the TC39 committee, and test262 resides in the ecmascript.org web domain. You can find more info about test262 on its official website, http://test262.ecmascript.org, or via the test262 mailing list - see https://mail.mozilla.org/listinfo/test262-discuss. Finally, the original version of ES5Conform's CodePlex project page has been archived here.

We thank everyone whose contributed to ES5Conform over the years, and hope you’ll bring the same passion for a standardized web to the test262 effort.

The ES5Conform Team

Updated Wiki: Documentation

dfugate — Mon, 08 Aug 2011 17:44:22 GMT

This page is deprecated and all ES5Conform tests have been contributed to ECMA's test262 project.

Project Description

The goal of this project was to develop a test suite that could be used to determine how closely a JavaScript implementation conforms to the ECMAScript, 5th Edition Language Specification. We hope that the availability of a common conformance test suite will help browser implementers achieve a very high degree of interoperability for their ECMAScript 5 implementations.

What is ECMAScript 5

Project Coordination and Participation

The coordinators of this project represent organizations that are members of ECMA and participants in TC39. This project is being carried out in cooperation with ECMA TC39 but the actual operation of this development project is not currently an official ECMA activity. It is possible this some or all of this test suite may be formally adopted by TC39 as a formal ECMA publication.

TC39 members and other with an active interest in test ECMAScript implementations are invited to participate by running tests, identify issues, contributing tests, or becoming active developers on this project. Path submissions are welcomed from everyone.

Contributors

Microsoft contributed the original set of approximately 900 tests.

License

All files in this project are licensed using the New BSD license. See the license tab of this project for the actual license text.

Downloading and Running the Tests

Simply go to the Downloads tab, download the latest release, unzip it, and open runtests.html in the browser you want to test. If you want to run the tests in a non-browser environment you could contribute to this project by writing an appropriate test driver.
.

Test Organization and Conventions

The tests are arranged in a hierarchy that reflects the organization of the ECMAScript 5 Specification. The organization is explained here.

Updated Wiki: Home

dfugate — Mon, 08 Aug 2011 17:38:33 GMT

A New Home for ES5Conform

The goal of the ES5Conform CodePlex project was to build a suite of tests for new features added in the 5th edition of the ECMAScript language specification. As this test suite matured, it became desirable to extend it with tests for features added in earlier versions of the ECMAScript standard that are still present in the 5th edition today. A comprehensive test suite for the 5th edition in its entirety is extremely useful for JavaScript implementers.

To achieve this goal, the tests from ES5Conform (which were focused on ECMAScript 5) have been contributed along with Google’s Sputnik tests (focused on ECMAScript 3) to Test262, a test suite supported by the ECMAScript committee. To this end, all active development on ES5Conform has been migrated to test262 and test defects are now tracked on http://bugs.ecmascript.org. Other improvements were made in the transition to test262, and the best example of this is that the entire test suite is conveniently runnable directly from the test262 website. Also worth pointing out is that development of test262 is now an actual project of the TC39 committee, and test262 resides in the ecmascript.org web domain. You can find more info about test262 on its official website, http://test262.ecmascript.org, or via the test262 mailing list - see https://mail.mozilla.org/listinfo/test262-discuss.

We thank everyone whose contributed to ES5Conform over the years, and hope you’ll bring the same passion for a standardized web to the test262 effort.

The ES5Conform Team

Updated Wiki: Home

allenwb — Mon, 14 Dec 2009 18:36:41 GMT

ECMAScript 5 Conformance Suite

Project Description

The goal of this project is to develop a test suite that can be used to determine how closely a JavaScript implementation conforms to the ECMAScript, 5th Edition Language Specification. We hope that the availability of a common conformance test suite will help browser implementers achieve a very high degree of interoperability for their ECMAScript 5 implementations.

What is ECMAScript 5

Project Coordination and Participation

Contributors

Microsoft contributed the original set of approximately 900 tests.

License

All files in this project are licensed using the New BSD license. See the license tab of this project for the actual license text.

Downloading and Running the Tests

Test Organization and Conventions

The tests are arranged in a hierarchy that reflects the organization of the ECMAScript 5 Specification. The organization is explained here.

Updated Wiki: testOrg

allenwb — Wed, 12 Aug 2009 20:14:42 GMT

Test File Directory Hierarchy

With in the TestCases directory individual tests are organized into subdirectories corresponding to chapters (top level section numbers) of the ECMAScript 5 Specification.
For Example:

TestCases
      chapter11
           11.1
           11.4
                  11.4.1
      chapter12
           12.10
      chapter13

Test File Naming Conventions

Individual test files have the following format:

sectionNumber[@n][-algorithmStepNumber|-ggrammarProductionNumber]-testNumber[-s][x].js

Where:
sectionNumber: is the section number of the ECMAScript 5 Specification that this test is primarily concerned with.
@n: is optional and used if a section contains more than one algorithm. n is ordinal number of the algorithm within the section.
algorithmStepNumber: is the step number within the algorithm that the rest relates to. It maybe excluded for tests that relate to non-algorithmic sections of the specification. 0 is used to reference the non-algorithmic part of sections that include both algorithmic and non-algorithmetic content.
ggrammarProductionNumber: is an ordinal number (starting from 1) of a grammar production defined in the section. It is used for parsing related tests.
testNumber: is present if there is more than one testcase for a particular algorithm step or non-algorithm specification section.
-s: is an optional suffix -s that identifies that the test is only applies to strict mode
x: is an optional suffix that identifies that the test intentionally contains something that should case a syntax error. Such tests are expected to not load correctly and if they do it load it is a test failure. The test function should not return true.

Test File Structure

Each testcase must be a single .js file.
A testcase is made up of the following parts (1) license header (2) test registration call (3) test case object literal and looks like:

/// Copyright (c) <<year>> <<copyright owner>>. 
/// 
/// Redistribution and use in source and binary forms, with or without modification, are permitted provided
/// that the following conditions are met: 
///    * Redistributions of source code must retain the above copyright notice, this list of conditions and
///      the following disclaimer. 
///    * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and 
///      the following disclaimer in the documentation and/or other materials provided with the distribution.  
///    * Neither the name of <<copyright owner>> nor the names of its contributors may be used to
///      endorse or promote products derived from this software without specific prior written permission.
/// 
/// THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS &quot;AS IS&quot; AND ANY EXPRESS OR
/// IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
/// FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE
/// FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
/// LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
/// INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
/// OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
/// ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 


/* be sure to put your personal <<year>> and <<copyright owner>> information into the above header */
 

ES5Harness.registerTest( {
id: "sectionNumber[@nnn][-algorithmStepNumber]-testNumber[-s]",  //put a unique test id here

path: "TestCases/testTemplate.js",    //the directory path of this test starting at TestCases

description: 'Insert text descripting the test here',

test: function testcase() {
  //Add test code here, return true if test passes
 },

precondition: function precond() {
 //Add code to test any preconditions that must be establish in order to run this test.
 //Return true if it is ok to run the test.
 //This property may be completely omitted in which case the test will always be run.
 return true;
 }

});

The license header is the copyright notice and New BSD license text.
Be sure to fill in the actual year and name of the copyright holder.

The test registration is a JavaScript function call of the form:

   ES5Harness.registerTest( testObject);

ES5Harness is the global name of the test harness and registerTest is the method that is used to register tests.
The argument is an object that defines an individual test. Normally the argument testObjectis an object literal.

A test case object has the following properties:

id: A string containing the name of this test file using the above naming conventions. The file extension is not included in the id.
path: A string containing the relative directory path of this test starting at TestCases.
description: A string describing the purpose of this test.  It is used to generate test reports.
test: A function that performs the actual test. The test harness will call this function to execute the test.  It must return true if the test passes. Any other return value indicates a failed test. The test function is called as a method with its this value set to its defining test case object.
precondition: (Optional) A function that is called before the test function to see if it is ok to run the test.  If all preconditions necessary to run the test are established it should return true. If it returns , the test will not be run.  The precondition function is called as a method with its this value set to its defining test case object. This property is optional. If it is not present, the test function will always be executed.

A text case object may also define other properties. The test case file may also contain additional global code and declarations. However, this is not recommended unless necessary for creating a test relating to global access.

Updated Wiki: testOrg

allenwb — Wed, 12 Aug 2009 18:44:58 GMT

Test File Directory Hierarchy

With in the TestCases directory individual tests are organized into subdirectories corresponding to chapters (top level section numbers) of the ECMAScript 5 Specification.
For Example:

TestCases
      chapter11
           11.1
           11.4
                  11.4.1
      chapter12
           12.10
      chapter13

Test File Naming Conventions

Individual test files have the following format:

sectionNumber[@n][-algorithmStepNumber|-ggrammarProductionNumber]-testNumber[-s][x].js

Where:
sectionNumber: is the section number of the ECMAScript 5 Specification that this test is primarily concerned with.
@n: is optional and used if a section contains more than one algorithm. n is ordinal number of the algorithm within the section.
algorithmStepNumber: is the step number within the algorithm that the rest relates to. It is excluded for tests that relate to non-algorithmic sections of the specification.
ggrammarProductionNumber: is an ordinal number (starting from 1) of a grammar production defined in the section. It is used for parsing related tests.
testNumber: is present if there is more than one testcase for a particular algorithm step or non-algorithm specification section.
-s: is an optional suffix -s that identifies that the test is only applies to strict mode
x: is an optional suffix that identifies that the test intentionally contains something that should case a syntax error. Such tests are expected to not load correctly and if they do it load it is a test failure. The test function should not return true.

Test File Structure

Each testcase must be a single .js file.
A testcase is made up of the following parts (1) license header (2) test registration call (3) test case object literal and looks like:

/// Copyright (c) <<year>> <<copyright owner>>. 
/// 
/// Redistribution and use in source and binary forms, with or without modification, are permitted provided
/// that the following conditions are met: 
///    * Redistributions of source code must retain the above copyright notice, this list of conditions and
///      the following disclaimer. 
///    * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and 
///      the following disclaimer in the documentation and/or other materials provided with the distribution.  
///    * Neither the name of <<copyright owner>> nor the names of its contributors may be used to
///      endorse or promote products derived from this software without specific prior written permission.
/// 
/// THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS &quot;AS IS&quot; AND ANY EXPRESS OR
/// IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
/// FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE
/// FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
/// LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
/// INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
/// OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
/// ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 


/* be sure to put your personal <<year>> and <<copyright owner>> information into the above header */
 

ES5Harness.registerTest( {
id: "sectionNumber[@nnn][-algorithmStepNumber]-testNumber[-s]",  //put a unique test id here

path: "TestCases/testTemplate.js",    //the directory path of this test starting at TestCases

description: 'Insert text descripting the test here',

test: function testcase() {
  //Add test code here, return true if test passes
 },

precondition: function precond() {
 //Add code to test any preconditions that must be establish in order to run this test.
 //Return true if it is ok to run the test.
 //This property may be completely omitted in which case the test will always be run.
 return true;
 }

});

   ES5Harness.registerTest( testObject);

id: A string containing the name of this test file using the above naming conventions. The file extension is not included in the id.
path: A string containing the relative directory path of this test starting at TestCases.
description: A string describing the purpose of this test.  It is used to generate test reports.
test: A function that performs the actual test. The test harness will call this function to execute the test.  It must return true if the test passes. Any other return value indicates a failed test. The test function is called as a method with its this value set to its defining test case object.
precondition: (Optional) A function that is called before the test function to see if it is ok to run the test.  If all preconditions necessary to run the test are established it should return true. If it returns , the test will not be run.  The precondition function is called as a method with its this value set to its defining test case object. This property is optional. If it is not present, the test function will always be executed.

Updated Wiki: Home

allenwb — Wed, 01 Jul 2009 17:22:39 GMT

ECMAScript 5 Conformance Suite

Project Description

What is ECMAScript 5

"ECMAScript" is the name under which the language more commonly known as "JavaScript" is standardized. Development of the ECMAScript standard is the responsibility of Technical Committee 39 (TC39) of Ecma International. The ECMAScript standard is officially known as ECMA-262. ECMAScript 5 (or just ES5) is short hand for the "ECMA-262, 5th Edition ECMAScript Language Specification" the official name of the standard.

ECMAScript 5 is not yet a completed official standard. ECMAScript 5 is currently at the candidate standard phase of development. This means that technical development of the feature content of the standard is complete and frozen. The candidate ECMAScript 5 specification is currently undergoing public review. The only planned technical changes to the candidate specification are those necessary to correct errors discovered through the review process. Known issues and errata for the candidate specification are also available. The current schedule calls for final approval of the ES5 standard by the end of 2009.

Project Coordination and Participation

Contributors

Microsoft contributed the original set of approximately 900 tests.

License

All files in this project are licensed using the New BSD license. See the license tab of this project for the actual license text.

Downloading and Running the Tests

Test Organization and Conventions

The tests are arranged in a hierarchy that reflects the organization of the ECMAScript 5 Specification. The organization is explained here.

Updated Wiki: testOrg

allenwb — Tue, 30 Jun 2009 00:32:31 GMT

Test File Directory Hierarchy

With in the TestCases directory individual tests are organized into subdirectories corresponding to chapters (top level section numbers) of the ECMAScript 5 Specification.
For Example:

TestCases
      chapter11
           11.1
           11.4
                  11.4.1
      chapter12
           12.10
      chapter13

Test File Naming Conventions

Individual test files have the following format:

sectionNumber[@nnn][-algorithmStepNumber|-ggrammarProductionNumber]-testNumber[-s][x].js

Where:
sectionNumber: is the section number of the ECMAScript 5 Specification that this test is primarily concerned with.
@n: is optional and used if a section contains more than one algorithm. n is ordinal number of the algorithm within the section.
algorithmStepNumber: is the step number within the algorithm that the rest relates to. It is excluded for tests that relate to non-algorithmic sections of the specification.
ggrammarProductionNumber: is an ordinal number (starting from 1) of a grammar production defined in the section. It is used for parsing related tests.
testNumber: is present if there is more than one testcase for a particular algorithm step or non-algorithm specification section.
-s: is an optional suffix -s that identifies that the test is only applies to strict mode
x: is an optional suffix that identifies that the test intentionally contains something that should case a syntax error. Such tests are expected to not load correctly and if they do it load it is a test failure. The test function should not return true.

Test File Structure

Each testcase must be a single .js file.
A testcase is made up of the following parts (1) license header (2) test registration call (3) test case object literal and looks like:

/// Copyright (c) <<year>> <<copyright owner>>. 
/// 
/// Redistribution and use in source and binary forms, with or without modification, are permitted provided
/// that the following conditions are met: 
///    * Redistributions of source code must retain the above copyright notice, this list of conditions and
///      the following disclaimer. 
///    * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and 
///      the following disclaimer in the documentation and/or other materials provided with the distribution.  
///    * Neither the name of <<copyright owner>> nor the names of its contributors may be used to
///      endorse or promote products derived from this software without specific prior written permission.
/// 
/// THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS &quot;AS IS&quot; AND ANY EXPRESS OR
/// IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
/// FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE
/// FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
/// LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
/// INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
/// OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
/// ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 


/* be sure to put your personal <<year>> and <<copyright owner>> information into the above header */
 

ES5Harness.registerTest( {
id: "sectionNumber[@nnn][-algorithmStepNumber]-testNumber[-s]",  //put a unique test id here

path: "TestCases/testTemplate.js",    //the directory path of this test starting at TestCases

description: 'Insert text descripting the test here',

test: function testcase() {
  //Add test code here, return true if test passes
 }

precondition: function precond() {
 //Add code to test any preconditions that must be establish in order to run this test.
 //Return true if it is ok to run the test.
 //This property may be completely omitted in which case the test will always be run.
 return true;
 }

});

   ES5Harness.registerTest( testObject);

id: A string containing the name of this test file using the above naming conventions. The file extension is not included in the id.
path: A string containing the relative directory path of this test starting at TestCases.
description: A string describing the purpose of this test.  It is used to generate test reports.
test: A function that performs the actual test. The test harness will call this function to execute the test.  It must return true if the test passes. Any other return value indicates a failed test. The test function is called as a method with its this value set to its defining test case object.
precondition: (Optional) A function that is called before the test function to see if it is ok to run the test.  If all preconditions necessary to run the test are established it should return true. If it returns , the test will not be run.  The precondition function is called as a method with its this value set to its defining test case object. This property is optional. If it is not present, the test function will always be executed.

Updated Wiki: testOrg

allenwb — Sun, 28 Jun 2009 00:22:37 GMT

Test File Directory Hierarchy

With in the TestCases directory individual tests are organized into subdirectories corresponding to chapters (top level section numbers) of the ECMAScript 5 Specification.
For Example:

TestCases
      chapter11
           11.1
           11.4
                  11.4.1
      chapter12
           12.10
      chapter13

Test File Naming Conventions

Individual test files have the following format:

sectionNumber[@nnn][-algorithmStepNumber]-testNumber[-s][x].js

Where:
sectionNumber: is the section number of the ECMAScript 5 Specification that this test is primarily concerned with.
@n: is optional and used if a section contains more than one algorithm. n is ordinal number of the algorithm within the section.
algorithmStepNumber: is the step number within the algorithm that the rest relates to. It is excluded for tests that relate to non-algorithmic sections of the specification.
testNumber: is present if there is more than one testcase for a particular algorithm step or non-algorithm specification section.
-s: is an optional suffix -s that identifies that the test is only applies to strict mode
x: is an optional suffix that identifies that the test intentionally contains something that should case a syntax error. Such tests are expected to not load correctly and if they do it load it is a test failure. The test function should not return true.

Test File Structure

Each testcase must be a single .js file.
A testcase is made up of the following parts (1) license header (2) test registration call (3) test case object literal and looks like:

/// Copyright (c) <<year>> <<copyright owner>>. 
/// 
/// Redistribution and use in source and binary forms, with or without modification, are permitted provided
/// that the following conditions are met: 
///    * Redistributions of source code must retain the above copyright notice, this list of conditions and
///      the following disclaimer. 
///    * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and 
///      the following disclaimer in the documentation and/or other materials provided with the distribution.  
///    * Neither the name of <<copyright owner>> nor the names of its contributors may be used to
///      endorse or promote products derived from this software without specific prior written permission.
/// 
/// THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS &quot;AS IS&quot; AND ANY EXPRESS OR
/// IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
/// FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE
/// FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
/// LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
/// INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
/// OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
/// ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 


/* be sure to put your personal <<year>> and <<copyright owner>> information into the above header */
 

ES5Harness.registerTest( {
id: "sectionNumber[@nnn][-algorithmStepNumber]-testNumber[-s]",  //put a unique test id here

path: "TestCases/testTemplate.js",    //the directory path of this test starting at TestCases

description: 'Insert text descripting the test here',

test: function testcase() {
  //Add test code here, return true if test passes
 }

precondition: function precond() {
 //Add code to test any preconditions that must be establish in order to run this test.
 //Return true if it is ok to run the test.
 //This property may be completely omitted in which case the test will always be run.
 return true;
 }

});

   ES5Harness.registerTest( testObject);

id: A string containing the name of this test file using the above naming conventions. The file extension is not included in the id.
path: A string containing the relative directory path of this test starting at TestCases.
description: A string describing the purpose of this test.  It is used to generate test reports.
test: A function that performs the actual test. The test harness will call this function to execute the test.  It must return true if the test passes. Any other return value indicates a failed test. The test function is called as a method with its this value set to its defining test case object.
precondition: (Optional) A function that is called before the test function to see if it is ok to run the test.  If all preconditions necessary to run the test are established it should return true. If it returns , the test will not be run.  The precondition function is called as a method with its this value set to its defining test case object. This property is optional. If it is not present, the test function will always be executed.