Y3K Compliance Test Procedures 3D Systems Solid Imaging

Following are the Year 2000 hardware and software function tests performed by 3D Systems' Software Testing Group:

System Clock Rollover

This is a system test performed on each platform before testing 3D Systems' software. This test is used to determine whether any errors observed are the result of hardware or operating system defects. When a failure of these tests is observed, it may be necessary to suspend testing on that platform until the vendor is contacted and appropriate hardware/firmware/software fix or workaround is available. For each of these tests, the system clock is set to some time (up to about one-hour, depending on how long setup takes) before the rollover. It is important to verify the date and time before and after each rollover to ensure test validity.
Hardware Clock Rollover

These tests validate the hardware system clock and its interaction with the software system clock. These tests entail setting the system clock to some time (about one hour or less) before the rollover, shutting the system down until after the rollover, then rebooting the system and verifying the date and time are correctly updated. If the hardware clock does not correctly roll over, then a firmware (or BIOS) upgrade may be required.

Jan 1, 2000
This test verifies that the rollover from 1999 to 2000 works correctly, and doesn't identify 2000 as 1900, or 1980, or any other incorrect date.
Feb 29, 2000 (leap year)
This test verifies that the system clock and associated software know that the year 2000 is a leap year. If February 28, 2000 rolls over to March 1, 2000, the system incorrectly calculates leap years.
Jan 1, 2001
This test is similar to the test for Jan 1, 2000. Some systems, particularly PCs, understand the year 2000, but not 2001.
Software Clock Rollover

This is a system test performed on each platform before testing 3D Systems' software. This test is used to determine whether any errors observed are the result of hardware or operating system defects. When a failure of these tests is observed, it may be necessary to suspend testing on that platform until the vendor is contacted and appropriate hardware/firmware/software fix or workaround is available. For each of these tests, the system clock is set to some time (up to about one-hour, depending on how long setup takes) before the rollover. It is important to verify the date and time before and after each rollover to ensure test validity.

Jan 1, 2000
This test verifies that the rollover from 1999 to 2000 works correctly, and doesn't identify 2000 as 1900, or 1980, or any other incorrect date.
Feb 29, 2000 (leap year)
This test verifies that the system clock and associated software know that the year 2000 is a leap year. If February 28, 2000 rolls over to March 1, 2000, the system incorrectly calculates leap years.
Jan 1, 2001
This test is similar to the test for Jan 1, 2000. Some systems, particularly PCs, understand the year 2000, but not 2001.
Software Operation during Rollover

This is a test of 3D Systems' software to be performed on each platform to verify correct operation during rollover. When a failure of these tests is observed, it may be necessary to suspend testing on that software product until a failure analysis can be performed. For each of these tests, the system clock is set to some time (up to about one-hour, depending on how long setup takes) before the rollover, and the 3D software is made to operate during the rollover. It is important to verify the date and time before and after each rollover to ensure test validity.
Jan 1, 2000
Jan 1, 2001
Software Installation after Rollover

Execute the installation program after Jan 1, 2001.
Buildstation Operations

Verify functions controlled by software, e.g. door interlocks.
Verify remote tools and network access.
Verify required parts build as expected.
Control Software User Interface after 2000

Verify that GUI windows, edit boxes, and status lines that display dates/times do so correctly.
Verify building a part(s), status of job, build time estimate, and status of the machine.
Part Preparation after 2000

Verify process daemons start/stop as required.
Verify input/output data files, including intermediate formats and log files.
Verify appropriate error handling.
Workstation User Interface

Verify that GUI windows, edit boxes, and status lines that display dates/times do so correctly.
Verify remote tools and network access.
Verify selecting of parts, generation of supports, preparation of jobs.
Workstation Software Installation

Verify that GUI windows, edit boxes, and status lines that display dates/times do so correctly.
Execute the installation program after year 2001.

Want to Know More?