CVS difference for acats/docs/mod_list.txt

Differences between 1.79 and version 1.80
Log of other versions for file acats/docs/mod_list.txt

--- acats/docs/mod_list.txt	2016/02/06 03:09:26	1.79
+++ acats/docs/mod_list.txt	2016/04/01 04:57:56	1.80
@@ -1,62 +1,174 @@
 ACATS Modification List for ACATS 4.0
-Version 4.0K
-February 6, 2016
+Version 4.0L
+March 31, 2016
 
 
 What is this?
 
-This is the ACATS modification list for ACATS 4.0. This document includes test corrections, test removals, and new tests for ACATS 4.0. ACATS 4.0 is the current test suite for Ada, covering the third edition of Ada, ISO/IEC 8652:2012 (usually known as "Ad
a 2012").
+This is the ACATS modification list for ACATS 4.0. This document includes test
+corrections, test removals, and new tests for ACATS 4.0. ACATS 4.0 is the
+current test suite for Ada, covering the third edition of Ada, ISO/IEC 8652:2012
+(usually known as "Ada 2012").
+
+ACATS Modification List version 3.1L for ACATS 3.1 is the current list for that
+test suite. ACATS 3.1 should be used for testing implementations that support
+Amendment 1 (ISO/IEC 8652:1995/AMD 1:2007, often known as "Ada 2005"), and will
+continue to be maintained as necessary for the foreseeable future.
+
+ACATS Modification List version 2.6D for ACATS 2.6 is the current list for that
+test suite. ACATS 2.6 should be used for testing implementations of the second
+edition of Ada, ISO/IEC 8652:1995 (usually known as "Ada 95"); it also will
+continue to be maintained as necessary for the foreseeable future.
 
-ACATS Modification List version 3.1L for ACATS 3.1 is the current list for that test suite. ACATS 3.1 should be used for testing implementations that support Amendment 1 (ISO/IEC 8652:1995/AMD 1:2007, often known as "Ada 2005"), and will continue to be ma
intained as necessary for the foreseeable future.
-
-ACATS Modification List version 2.6D for ACATS 2.6 is the current list for that test suite. ACATS 2.6 should be used for testing implementations of the second edition of Ada, ISO/IEC 8652:1995 (usually known as "Ada 95"); it also will continue to be maint
ained as necessary for the foreseeable future.
-
 Changes from the last list:
-
-Note that there is no modification list 4.0I, as I can be confused with 1.
-
-New test C3A0030 checks that access discriminants only exclude null if they include a null exclusion. This is an inconsistency between Ada 95 and Ada 2005 that does not appear to have been previously tested.
-
-New test C480001 checks that dynamic accessibility checks are made on class-wide allocators.
-
-New test C650B04 checks that accessibility checks are made on the objects returned from a function with a class-wide return type.
-
-Test B480003 was modified to correct the test objective and test description to actually describe the test; the objective mentioned qualified expressions (none in uninitialized allocators), and the test description was unmodified from the older test that 
had served as a template (thus discussing return statements, not relevant for a test about allocators). The actual test code is unchanged.
-
-New tests B611001 through B611006 check various rules about preconditions and postconditions.
 
-Test B750A07 was modified to correct the test objective; the objective was unintentionally the same as the parent test, and never mentioned expression functions.
+Test B611006 was corrected that operations Proc3 and Proc4 are abstract (the
+precondition would be illegal for a null procedure). Tests B480003, B611001,
+B611002, B611003, B611004, B611005, B750A07, BB42001, BB42002, and BB42003 were
+updated with error location codes; these tell the future grading tools (see
+discussion below) exactly where an error should be expected. (All future new
+tests will also have these codes.)
+
+New tests B611007, B611008, B611009, B611010, B611011, B611012, B611013,
+C611A01, C611A02, C611A03, C611B01, and C611B02 check additional objectives for
+preconditions, postconditions, and related attributes.
+
+Test CD11001 had an incorrect value (which caused an unexpected
+Assertion_Error).
+
+The support files REPSPEC.ADA and REPBODY.ADA have been replaced by file
+REPORT.A. (More discussion below.)
+
+New tests posted between January 1, 2016 and March 31, 2016 will become required
+for conformity assessments on October 1, 2016. New tests posted between October
+1, 2015 and December 31, 2015 will become required for conformity assessments on
+July 1, 2016. New tests posted between July 1, 2015 and September 30, 2015 will
+become required for conformity assessments on April 1, 2016. New tests posted
+before June 30, 2015 are now required for conformity assessments. All tests
+posted to modification lists for other versions of the ACATS are included in
+ACATS 4.0 if appropriate and thus are required for conformity assessment using
+ACATS 4.0 The effective dates of tests are marked in the lists.
 
-Test C760015 was modified so that the expected result of Subtest2(4) was correct.
+Questions about this document? Contact the ACAA Technical Agent at
+agent@ada-auth.org.
 
-New tests BB42001, BB42002, BB42003, CB42001, CB42002, and CB42003 test a variety of rules about pragmas Assert and Assertion_Policy.
-
-Many tests changed status on January 1st, this list reflects those changes.
-
-New tests posted between January 1, 2016 and March 31, 2016 will become required for conformity assessments on October 1, 2016. New tests posted between October 1, 2015 and December 31, 2015 will become required for conformity assessments on July 1, 2016.
 New tests posted between July 1, 2015 and September 30, 2015 will become required for conformity assessments on April 1, 2016. New tests posted before June 30, 2015 are now required for conformity assessments. All tests posted to modification lists for ot
her versions of the ACATS are included in ACATS 4.0 if appropriate and thus are required for conformity assessment using ACATS 4.0 The effective dates of tests are marked in the lists. 
-
-Questions about this document? Contact the ACAA Technical Agent at agent@ada-auth.org.
-
 Technical Corrigendum 1:
 
-Beginning with ACATS Modification List 4.0B, we have included tests for corrections (including new features) in Technical Corrigendum 1, ISO/IEC 8652:2012/Cor 1:2016. All of these changes are corrections to Ada 2012; as such we will assume all such correc
tions are implemented in Ada 2012 compilers.
+Beginning with ACATS Modification List 4.0B, we have included tests for
+corrections (including new features) in Technical Corrigendum 1, ISO/IEC
+8652:2012/Cor 1:2016. All of these changes are corrections to Ada 2012; as such
+we will assume all such corrections are implemented in Ada 2012 compilers.
+
+ACATS 4.1 Announced
+
+The ACAA has announced its intention to create a new version of the ACATS under
+the baselining policy. Such a new ACATS version will include new and modified
+test files that are effective by the official use date of the new ACATS (in this
+case, July 1, 2016).
+
+ACATS 4.1 will include optional Test Grading tools
+
+ACATS 4.1 will introduce new test grading tools. The new version of Report
+included in this ACATS Modification List is the first piece of those tools.
+
+When the ACATS was designed (as the ACVC in the early 1980s), the intention
+always was that running it would give a simple and clear Pass or Fail result.
+However, grading of tests (particularly of B and L Tests) is somewhat subjective
+and very time-consuming. (Test grading typically involved poring over compiler
+listings of the entire ACATS with a large highlighter.) The subjectivity was
+acceptable in the days of common formal testing, as the formal testers would
+enforce a common grading standard (even if no one could describe what that was),
+but in an age of self-testing, it reduces the value of the ACATS.
+
+As such, we're introducing a long-overdue set of automated grading tools. These
+tools are intended to:
+* Greatly reduce the effort to grade an ACATS test run (and, hopefully to reduce
+  the cost of formal testing to make it a more practical option);
+* Ensure that all users of the ACATS grade tests in the same way, thus making it
+  more valid to compare ACATS results between different implementations and
+  different testers;
+* Give implementers certainty as to whether a particular test result is passing
+  (whether the location of an error is “close enough” to the canonical
+  position);
+* Be able to detect process errors (especially errors of omission) – that is,
+  tests improperly run (for instance, files compiled in the wrong order where
+  the ACATS requires an order), or not run at all (if one is checking off lines
+  in a listing, it's hard to notice that some test or portion of a test is
+  missing).
+
+The tools also will optionally give feedback to implementers about quality of
+error message positioning and of error cascades (does one error generate
+multiple messages?). (Since “goodness of an implementation” is not something
+that the ACATS tests for, this is not an official goal for the tools.)
+
+This is an ambitious set of goals. It's unlikely that they'll be completely met
+by the initial versions of the tools. As such, their use will be completely
+optional (but encouraged!) for ACATS 4.1. The tools will be updated periodically
+by the normal process for updating the ACATS – an ACATS Modification List like
+this one.
+
+It's probably obvious to most readers that these grading tools will require the
+compiler and binder output to be put into a common form (called an "event trace"
+in ACATS 4.1). We've settled on a .csv file format, as it is simple to write in
+an Ada program, easy to check in any spreadsheet program, and relatively easy to
+read in Ada code. To see an example, look at the new version of the Report
+package. The 60-line Put_Event_Trace routine writes a single event to the trace
+file. Most of the code is related to ensuring that the message doesn't contain
+any double quote characters, and to truncating the message to a reasonable
+length.
+
+There are two ways to put event trace construction into an existing Ada
+implementation. One is to add compiler and binder switches to turn on event
+trace writing. The compiler and binder would then write events in their error
+handlers and other strategic locations. Combined with the event writing in
+Report (by changing the Generate_Event_Trace_File constant to True), a complete
+event trace can easily be created for any portion of a test run.
+
+Alternatively, one could create a program to analyze a compiler/binder/run
+listing and convert the events found in it to appropriate event trace events.
+With such a tool, all of the events would be extracted from the listing, and the
+event writing in Report would not be used. This approach would be more
+appropriate if the ACATS user cannot change the compiler and/or binder.
+
+Much more on this topic, and related topics, will be found in the ACATS 4.1
+documentation. As always, if you have questions or would like to volunteer to
+help test the tools, contact the ACAA Technical Agent at agent@ada-auth.org.
 
 Notice:
 
-The ACAA has created and maintains the Ada Conformity Assessment Test Suite for the purpose of conformity assessments conducted in accordance with the International Standard ISO/IEC 18009 - Ada: Conformity assessment of a language processor. This test sui
te should not be used to make claims of conformance unless used in accordance with ISO/IEC 18009 and any applicable ACAA procedures.
+The ACAA has created and maintains the Ada Conformity Assessment Test Suite for
+the purpose of conformity assessments conducted in accordance with the
+International Standard ISO/IEC 18009 - Ada: Conformity assessment of a language
+processor. This test suite should not be used to make claims of conformance
+unless used in accordance with ISO/IEC 18009 and any applicable ACAA procedures.
 
 List explanation:
 
-Test numbers given are for the basic test.  Categories are “Withdrawn” (the test should not be processed for Ada conformity assessments); “Allowed Modification” (either the original test or the modified one should be processed for Ada conformity assessmen
ts); “Modified” (the modified test must be processed for Ada conformity assessments); “Pending New” (the test does not need to be processed for Ada conformity assessments, but will be added in the future); “New” (the test is processed for Ada conformity as
sessments).
+Test numbers given are for the basic test.  Categories are “Withdrawn” (the test
+should not be processed for Ada conformity assessments); “Allowed Modification”
+(either the original test or the modified one should be processed for Ada
+conformity assessments); “Modified” (the modified test must be processed for Ada
+conformity assessments); “Pending New” (the test does not need to be processed
+for Ada conformity assessments, but will be added in the future); “New” (the
+test is processed for Ada conformity assessments).
+
+ACATS version labels are provided with all new and modified tests. Use this
+label to retrieve the test from the ACATS VCS. See “How to get new and modified
+tests”.
+
+In citations, line numbers are given relative to the start of a test file in the
+format of '@<line#,line#,...>'; if a test program comprises more than one file,
+then the particular file will be indicated by "fn", where "n" is the
+test-program name's file-designator numeral.  E.g., "B38103E : @f1-31, ... "
+denotes test file b38103e1.ada. In cases where there are two or more rationales
+for different errors in a test program, these different rationales with their
+respective line citations are listed on separate lines.  References to the Ada
+standards are given in the format:
 
-ACATS version labels are provided with all new and modified tests. Use this label to retrieve the test from the ACATS VCS. See “How to get new and modified tests”.
-
-In citations, line numbers are given relative to the start of a test file in the format of '@<line#,line#,...>'; if a test program comprises more than one file, then the particular file will be indicated by "fn", where "n" is the test-program name's file-
designator numeral.  E.g., "B38103E : @f1-31, ... " denotes test file
-b38103e1.ada. In cases where there are two or more rationales for different errors in a test program, these different rationales with their respective line citations are listed on separate lines.  References to the Ada standards are given in the format:
-
 	<section|chapter>.<clause>[.<subclause>]:<paragraph>
 
-These references are to the Ada standard as available at http://www.adaic.org/resources/add-contentstandards/12rm/html/RM-TOC.html.
+These references are to the Ada standard as available at
+http://www.adaic.org/resources/add-contentstandards/12rm/html/RM-TOC.html.
 
 
 
@@ -315,10 +427,11 @@
 	object whose type is more local than the access type.
 	[VCS Label A4_0E] Eliminated overlong lines and tab characters.
 
-B480003 [Allowed Modification] New VCS Label: A4_0K Org VCS Label: A4_0E
+B480003 [Allowed Modification] New VCS Label: A4_0L Org VCS Label: A4_0E
 			Required after 2016-07-01
 	[VCS Label A4_0K] Corrected test objective and test description;
 	the test code is unmodified.
+	[VCS Label A4_0L] Added error location codes.
 
 C540002 [Modified] VCS Label: A4_0E
 	Eliminated overlong lines.
@@ -368,36 +481,105 @@
 	Check legality rules for generalized iterators from Technical
 	Corrigendum 1.
 
-B611001 [Pending New] New VCS Label: A4_0K
+B611001 [Pending New] New VCS Label: A4_0L
 			Required after 2016-10-01
-	Check that Pre and Post are only allowed on subprograms and
-	entries (and not on subprogram instances).
+	[VCS Label A4_0K] Check that Pre and Post are only allowed on
+	subprograms and entries (and not on subprogram instances).
+	[VCS Label A4_0L] Added error location codes.
 
-B611002 [Pending New] New VCS Label: A4_0K
+B611002 [Pending New] New VCS Label: A4_0L
 			Required after 2016-10-01
-	Check that Pre and Post are not allowed on subprograms acting as
-	completions.
+	[VCS Label A4_0K] Check that Pre and Post are not allowed on
+	subprograms acting as completions.
+	[VCS Label A4_0L] Added error location codes.
 
-B611003 [Pending New] New VCS Label: A4_0K
+B611003 [Pending New] New VCS Label: A4_0L
 			Required after 2016-10-01
-	Check that Pre'Class and Post'Class are only allowed on primitive
-	subprograms of tagged types. (Normal tagged types and interfaces.)
+	[VCS Label A4_0K] Check that Pre'Class and Post'Class are only
+	allowed on primitive subprograms of tagged types. (Normal tagged
+	types and interfaces.)
+	[VCS Label A4_0L] Added error location codes.
 
-B611004 [Pending New] New VCS Label: A4_0K
+B611004 [Pending New] New VCS Label: A4_0L
 			Required after 2016-10-01
-	Check that Pre'Class and Post'Class are not allowed on
-	subprograms acting as completions.
+	[VCS Label A4_0K] Check that Pre'Class and Post'Class are not
+	allowed on subprograms acting as completions.
+	[VCS Label A4_0L] Added error location codes.
 
-B611005 [Pending New] New VCS Label: A4_0K
+B611005 [Pending New] New VCS Label: A4_0L
 			Required after 2016-10-01
-	Check that Pre and Post are not allowed on abstract subprograms
-	and null procedures.
+	[VCS Label A4_0K] Check that Pre and Post are not allowed on
+	abstract subprograms and null procedures.
+	[VCS Label A4_0L] Added error location codes.
 
-B611006 [Pending New] New VCS Label: A4_0K
+B611006 [Pending New] New VCS Label: A4_0L
 			Required after 2016-10-01
-	Check that the restrictions on Pre'Class and Post'Class
-	expressions added by AI12-0113-1 are enforced.
+	[VCS Label A4_0K] Check that the restrictions on Pre'Class and
+	Post'Class expressions added by AI12-0113-1 are enforced.
+	[VCS Label A4_0L] Proc3 @88 and Proc4 @91 need to be abstract in
+	order to avoid failing 6.1.1(18.1/4).
 
+B611007 [Pending New] New VCS Label: A4_0L
+			Required after 2016-10-01
+	Check that Pre'Class and Post'Class are not allowed on entries
+	and protected subprograms of untagged task and protected types.
+
+B611008 [Pending New] New VCS Label: A4_0L
+			Required after 2016-10-01
+	Check various rules about the use of the Result attribute.
+
+B611009 [Pending New] New VCS Label: A4_0L
+			Required after 2016-10-01
+	Check that F'Result is not allowed in the body of F.
+
+B611010 [Pending New] New VCS Label: A4_0L
+			Required after 2016-10-01
+	Check that the Old attribute is not allowed in a subprogram or
+	entry body, or in an accept statement.
+
+B611011 [Pending New] New VCS Label: A4_0L
+			Required after 2016-10-01
+	Check the Old attribute cannot be used within a precondition
+	expression nor in a generic specification outside of a
+	postcondition expression.
+
+B611012 [Pending New] New VCS Label: A4_0L
+			Required after 2016-10-01
+	Check that the prefix of an Old attribute cannot contain the
+	Result attribute, another Old attribute, nor the index of a
+	quantified expression.
+
+B611013 [Pending New] New VCS Label: A4_0L
+			Required after 2016-10-01
+	For a discrete X, check that X'Old has the nominal subtype of X.
+
+C611A01 [Pending New] New VCS Label: A4_0L
+			Required after 2016-10-01
+	Check that preconditions and postconditions where both specific
+	and class-wide contracts apply are checked properly.
+
+C611A02 [Pending New] New VCS Label: A4_0L
+			Required after 2016-10-01
+	Check that the correct expressions are evaluated for specific
+	preconditions and postconditions, and that they are evaluated
+	at the correct point.
+
+C611A03 [Pending New] New VCS Label: A4_0L
+			Required after 2016-10-01
+	Check that the correct expressions are evaluated for class-wide
+	preconditions and postconditions, and that they are evaluated
+	at the correct point.
+
+C611B01 [Pending New] New VCS Label: A4_0L
+			Required after 2016-10-01
+	Check that X'Old has the tag of X and not the tag of the nominal
+	subtype of X (for Post).
+
+C611B02 [Pending New] New VCS Label: A4_0L
+			Required after 2016-10-01
+	Check that X'Old has the tag of X and not the tag of the nominal
+	subtype of X (for Post'Class).
+
 B640001 [New] VCS Label: A4_0E
 	[VCS Label A4_0C] Check that abstract nondispatching operations
 	do not participate in resolution.
@@ -530,13 +712,14 @@
 	of a simple return statement for a function that returns a
 	limited type.
 
-B750A07 [Pending New] New VCS Label: A4_0H
+B750A07 [Pending New] New VCS Label: A4_0L
 			Required after 2016-10-01
 	[VCS Label A4_0H] Check that only legal expressions are allowed
 	in the return expression of an expression function that returns a
 	limited type.
 	[VCS Label A4_0K] Corrected objective to mention “expression
 	functions”.
+	[VCS Label A4_0L] Added error location codes.
 
 B750A08 [Pending New] New VCS Label: A4_0H
 			Required after 2016-04-01
@@ -639,20 +822,23 @@
 	retrieved with Exception_Message.
 	[VCS Label A4_0E] Eliminated overlong lines and tab characters.
 
-BB42001 [Pending New] New VCS Label: A4_0K
+BB42001 [Pending New] New VCS Label: A4_0L
 			Required after 2016-10-01
-	Check that the arguments of a pragma Assert have to have the
-	correct types.
+	[VCS Label A4_0K] Check that the arguments of a pragma Assert
+	have to have the correct types.
+	[VCS Label A4_0L] Added error location codes.
 
 CB42001 [Pending New] New VCS Label: A4_0K
 			Required after 2016-10-01
 	Check the usual operation of pragma Assert, including the optional
 	message.
 
-BB42002 [Pending New] New VCS Label: A4_0K
+BB42002 [Pending New] New VCS Label: A4_0L
 			Required after 2016-10-01
-	Check that the arguments of a pragma Assert cannot be reordered
+	[VCS Label A4_0K] Check that the arguments of a pragma Assert
+	cannot be reordered
 	even if named notation is used.
+	[VCS Label A4_0L] Added error location codes.
 
 CB42002 [Pending New] New VCS Label: A4_0K
 			Required after 2016-10-01
@@ -660,10 +846,11 @@
 	expressions of a pragma Assert are evaluated and no exception is
 	raised by the pragma.
 
-BB42003 [Pending New] New VCS Label: A4_0K
+BB42003 [Pending New] New VCS Label: A4_0L
 			Required after 2016-10-01
-	Check that a pragma Assertion_Policy is illegal if the policy is
-	not recognized.
+	[VCS Label A4_0K] Check that a pragma Assertion_Policy is illegal
+	if the policy is not recognized.
+	[VCS Label A4_0L] Added error location codes.
 
 CB42003 [Pending New] New VCS Label: A4_0K
 			Required after 2016-10-01
@@ -705,6 +892,17 @@
 	Check that a call on a formal abstract subprogram must be
 	dispatching.
 
+CD11001 [Pending New] New VCS Label: A4_0L
+			Required after 2016-10-01
+	[VCS Label A4_0J] Check that appropriate entities are visible in
+	an aspect specification.
+	[VCS Label A4_0L] Value 12 @121 should have been 52.
+
+BD11002 [Pending New] New VCS Label: A4_0J
+			Required after 2016-07-01
+	Check that entities in the private part of a package are not
+	visible in aspect specifications given in the visible part.
+
 CD30006 [Modified] VCS Label: A4_0E
 	Eliminated overlong lines and tab characters.
 
@@ -723,22 +921,12 @@
 	The test is unchanged other than renaming the units involved
 	and fixing an overlong line.
 
-CC33001 [Withdrawn] VCS Label: A4_0J
+CD33001 [Withdrawn] VCS Label: A4_0J
 	Renamed to CD30008, as there is no subclause 13.3.3.
 
-CC33002 [Withdrawn] VCS Label: A4_0J
+CD33002 [Withdrawn] VCS Label: A4_0J
 	Renamed to CD30009, as there is no subclause 13.3.3.
 
-CD11001 [Pending New] New VCS Label: A4_0J
-			Required after 2016-07-01
-	Check that appropriate entities are visible in an aspect
-	specification.
-
-BD11002 [Pending New] New VCS Label: A4_0J
-			Required after 2016-07-01
-	Check that entities in the private part of a package are not
-	visible in aspect specifications given in the visible part.
-
 BDB3A01 [New] VCS Label: A4_0E
 	[VCS Label A4_0B] Test resolution and legality rules for
 	pragma and aspect Default_Storage_Pool.
@@ -943,6 +1131,14 @@
 	Bingo_Call value rather than a reference, (and then was renamed)
 	in order to prevent an accessibility failure.
 
+F611A00 [Pending New] New VCS Label: A4_0L
+			Required after 2016-10-01
+	Foundation for tests C611A01, C611A02, and C611A03.
+
+F611B00 [Pending New] New VCS Label: A4_0L
+			Required after 2016-10-01
+	Foundation for tests C611B01 and C611B02.
+
 F650B00 [Pending New] New VCS Label: A4_0H
 			Required after 2016-04-01
 	Foundation for tests C650B01, C650B02, and C650B03.
@@ -982,17 +1178,34 @@
 	imported routines in tests CXB3023 and CXB3024. The change is only
 	needed for those tests, it has no effect on any other test.
 
+REPORT [Allowed Modification] New VCS Label: A4_0L Org VCS Label: A4_0
+			Required after 2016-07-01
+	[VCS Label A4_0L] Revised to modern format, added optional
+	event trace creation. (More discussion in introduction.) Note that
+	the support file has been renamed to a modern name REPORT.A; the
+	older files REPSPEC.ADA and REPBODY.ADA are replaced. This changed
+	file mainly is intended to support new capabilities in ACATS 4.1.
+
 
 
 How to get new and modified tests:
 
-The official home of the ACATS test suite is the ACAA web site. The site can be accessed at www.ada-auth.org.
+The official home of the ACATS test suite is the ACAA web site. The site can be
+accessed at www.ada-auth.org.
 
-The complete set of official new and modified tests are available in the Mod_4_0K.Zip and Tar files on the ACAA web site.
+The complete set of official new and modified tests are available in the
+Mod_4_0L.Zip and Tar files on the ACAA web site.
 
-Individual new and modified tests can be retrieved from the ACATS VCS. Simply navigate to the appropriate directory (folder), and select the test you want. Select the revision you want (usually the most recent) and it will be retrieved for you. Tests are 
stored in directories that correspond to the test’s prefix. For instance, the test CD92001.A will be found in the CD directory. You can also browse the differences between versions of a test. [In case of a conflict, the files in the ACATS VCS should be con
sidered the 'official' versions.]
+Individual new and modified tests can be retrieved from the ACATS VCS. Simply
+navigate to the appropriate directory (folder), and select the test you want.
+Select the revision you want (usually the most recent) and it will be retrieved
+for you. Tests are stored in directories that correspond to the test’s prefix.
+For instance, the test CD92001.A will be found in the CD directory. You can also
+browse the differences between versions of a test. [In case of a conflict, the
+files in the ACATS VCS should be considered the 'official' versions.]
 
-If you cannot get the files from the official site or you cannot get the files in a format appropriate for your processor, please contact your ACAL.
+If you cannot get the files from the official site or you cannot get the files
+in a format appropriate for your processor, please contact your ACAL.
 
 The baseline ACATS 4.0 is available in various formats on the ACAA web site.
 
@@ -1012,9 +1225,10 @@
 
 (Refer to the main list for details)
 
-B480003	2016-07-01 [VCS Label A4_0K]
-C760015	2016-07-01 [VCS Label A4_0K]
+B480003	2016-07-01 [VCS Label A4_0L]
+C760015	2016-07-01 [VCS Label A4_0L]
 IMPDEF	2016-04-01 [Only needed for new tests CXB3023 and CXB3024]
+REPORT	2016-07-01 [Only needed in ACATS 4.1]
 
 
 
@@ -1171,6 +1385,13 @@
 B611004	2016-10-01
 B611005	2016-10-01
 B611006	2016-10-01
+B611007	2016-10-01
+B611008	2016-10-01
+B611009	2016-10-01
+B611010	2016-10-01
+B611011	2016-10-01
+B611012	2016-10-01
+B611013	2016-10-01
 B750A04	2016-04-01
 B750A05	2016-04-01
 B750A06	2016-04-01
@@ -1195,6 +1416,11 @@
 C457007	2016-07-01
 C480001	2016-10-01
 C540003	2016-07-01
+C611A01	2016-10-01
+C611A02	2016-10-01
+C611A03	2016-10-01
+C611B01	2016-10-01
+C611B02	2016-10-01
 C650A02	2016-04-01
 C650B01	2016-04-01
 C650B02	2016-04-01
@@ -1203,11 +1429,14 @@
 CB42001	2016-10-01
 CB42002	2016-10-01
 CB42003	2016-10-01
-CD11001	2016-07-01
+CD11001	2016-10-01
 CD30008	2016-07-01
 CD30009	2016-07-01
 CXAC008	2016-04-01
 CXB3023	2016-07-01
 CXB3024	2016-07-01
+F611A00	2016-10-01
+F611B00	2016-10-01
 F650B00	2016-04-01
+
 

Questions? Ask the ACAA Technical Agent