Abstract: In one aspect, identification and communication systems are described herein. An identification and communication system described herein, in some embodiments, comprises one or more query units and one or more response units, wherein at least one response unit comprises one or more detectors comprising one or more optical fibers operable to direct one or more signals received from at least one query unit to the one or more detectors. In some embodiments, at least one optical fiber is operable to receive a signal from at least one query unit through the side of the optical fiber. In some embodiments, at least one optical fiber comprises a fluorescent plastic fiber (FPF). In some embodiments, at least one optical fiber is disposed in a textile.

Abstract: In one aspect, identification and communication systems are described herein. In some embodiments, an identification and communication system comprises one or more query units and one or more response units, wherein at least one query unit comprises a query beam source comprising a light emitting diode (LED) operable to emit a query beam. In some embodiments, the query beam is substantially collimated. In some embodiments, an identification and communication system comprises one or more query units and one or more response units, wherein at least one query unit comprises a first query beam source operable to emit a first component beam and a second query beam source operable to emit a second component beam. In some embodiments, the first query beam source comprises an LED and the second query beam source comprises a laser. In some embodiments, the first component beam and the second component beam are substantially concentric.

Abstract: In some embodiments, an identification and communication system described herein comprises one or more query units and one or more response units, wherein at least one query unit comprises a query beam source operable to emit a query beam and at least one response unit comprises at least one detector comprising an application specific integrated circuit (ASIC) comprising an amplifier operable to amplify the query beam. In some embodiments, a system comprises one or more query units and one or more response units, wherein at least one response unit comprises at least one detector capable of detecting incident radiation having a power of about 100 pW or less. In some embodiments, a system comprises at least one component of a response unit disposed in a first housing mounted to a weapon and at least one component of a query unit disposed in a second housing mounted to the weapon.

Abstract: In one aspect, identification and communication systems are described herein. In some embodiments, an identification and communication system comprises one or more query units and one or more response units, wherein at least one query unit is a handheld device. In some embodiments, the handheld device does not comprise a weapon and is not mounted on a weapon. In some embodiments, the handheld device comprises a flashlight. In some embodiments, the handheld device comprises a stylus. In some embodiments, the handheld device comprises a smart device in communication with the stylus. In some embodiments, the handheld device comprises a display screen. In some embodiments, the handheld device comprises a query controller and the display screen is operable to display data provided by the query controller.

Abstract: In some embodiments, a method of simulating combat described herein comprises emitting a first query beam from a first query unit of a first interoperable identification and communication system, receiving the first query beam with a second response unit of a second interoperable identification and communication system, emitting a second response beam with the second response unit, and receiving the second response beam with the first query unit. In some embodiments, a method of simulating combat comprises emitting a query beam comprising a plurality of packets each comprising a header portion, an information portion, and a footer portion from a query unit; and receiving the query beam with a response unit comprising a plurality of detectors spatially separated from one another, wherein the response unit is operable to independently measure the intensity of each packet of the query beam received at each of the plurality of detectors.

Abstract: In some embodiments, an identification and communication system described herein comprises one or more query units and one or more response units, wherein at least one query unit comprises a query beam source operable to emit a query beam and at least one response unit comprises at least one detector comprising an application specific integrated circuit (ASIC) comprising an amplifier operable to amplify the query beam. In some embodiments, a system comprises one or more query units and one or more response units, wherein at least one response unit comprises at least one detector capable of detecting incident radiation having a power of about 100 pW or less. In some embodiments, a system comprises at least one component of a response unit disposed in a first housing mounted to a weapon and at least one component of a query unit disposed in a second housing mounted to the weapon.

Abstract: In some embodiments, a method of simulating combat described herein comprises emitting a first query beam from a first query unit of a first interoperable identification and communication system, receiving the first query beam with a second response unit of a second interoperable identification and communication system, emitting a second response beam with the second response unit, and receiving the second response beam with the first query unit. In some embodiments, a method of simulating combat comprises emitting a query beam comprising a plurality of packets each comprising a header portion, an information portion, and a footer portion from a query unit; and receiving the query beam with a response unit comprising a plurality of detectors spatially separated from one another, wherein the response unit is operable to independently measure the intensity of each packet of the query beam received at each of the plurality of detectors.

Abstract: In one aspect, identification and communication systems are described herein. In some embodiments, an identification and communication system comprises one or more query units and one or more response units, wherein at least one query unit is a handheld device. In some embodiments, the handheld device does not comprise a weapon and is not mounted on a weapon. In some embodiments, the handheld device comprises a flashlight. In some embodiments, the handheld device comprises a stylus. In some embodiments, the handheld device comprises a smart device in communication with the stylus. In some embodiments, the handheld device comprises a display screen. In some embodiments, the handheld device comprises a query controller and the display screen is operable to display data provided by the query controller.

Abstract: In one aspect, identification and communication systems are described herein. In some embodiments, an identification and communication system comprises one or more query units and one or more response units, wherein at least one query unit comprises a query beam source comprising a light emitting diode (LED) operable to emit a query beam. In some embodiments, the query beam is substantially collimated. In some embodiments, an identification and communication system comprises one or more query units and one or more response units, wherein at least one query unit comprises a first query beam source operable to emit a first component beam and a second query beam source operable to emit a second component beam. In some embodiments, the first query beam source comprises an LED and the second query beam source comprises a laser. In some embodiments, the first component beam and the second component beam are substantially concentric.

Abstract: In one aspect, identification and communication systems are described herein. An identification and communication system described herein, in some embodiments, comprises one or more query units and one or more response units, wherein at least one response unit comprises one or more detectors comprising one or more optical fibers operable to direct one or more signals received from at least one query unit to the one or more detectors. In some embodiments, at least one optical fiber is operable to receive a signal from at least one query unit through the side of the optical fiber. In some embodiments, at least one optical fiber comprises a fluorescent plastic fiber (FPF). In some embodiments, at least one optical fiber is disposed in a textile.

Abstract: Software (such as server products) operating in a complex networked environment often run on multi-machine installations that are known as machine clusters. A server product can be tested on a server machine type. The server product can be tested by tracking the constituent machines of a machine cluster, and configuring and recording the roles that each machine in the machine cluster plays. Scenarios targeting a single server machine-type can be seamlessly mapped from the single machine scenario to a machine cluster of any number of machines, while handling actions such as executing tests and gathering log files from all machines of a machine cluster as a unit.

Abstract: An integrated test framework is disclosed that allows software testers to easily generate and execute tests of software involving multiple interacting computer systems. A copy of the integrated test framework resides on each computer system in the test. The integrated test framework on each computer system supports the independent testing of software on that system and also the synchronization between the computer systems. A test manager is provided to coordinate the synchronization. All the information necessary to direct the test framework on each of the computer systems is included within a single test script that is propagated to and executed on each computer system. The test script dictates the role of each computer system within the test and includes role specific actions and identifies points at which the computer systems must synchronize together for the passing of data, messages or other communications.

Abstract: A test services provider is an object that is arranged to provide a standardized interface for calling test harness provided functionality. The test services provider is not tied to a specific test harness, and provides a standard interface such that both test harness functionality and test cases can be written without beforehand knowledge of the other. In operation, the test harness registers the test services that provides with the test service provider, and the test cases retrieve the registered test services from the test harness as needed. Accordingly, the test case does not have to query the test harness itself for the object that provides the desired test harness functionality, but rather uses a standardized interface provided by the test services provider to retrieve the desired test services.

Abstract: Software automation testing and validation are provided according to a system that runs automation tests using multiple lab machines and allows the testing to be performed before checking in the code to a version control system. Code changes in a build of the software are provided on a computing device. Automation tests are selected from a list of available tests. When indicated by a job queue, the changed code of the build is forwarded to lab machines allocated by an automation system. An image of the build from the computing device is generated on the lab machines and the automation tests are run against the build. A report is generated and forwarded back to one or more recipients that notifies of the success or failure of the automation testing.

Abstract: The present invention is directed towards a test case inheritance behavior that can be controlled via attributes. A base test class from which test objects are derived are useful for reducing test case code and management. For example, base test classes and their derived objects can be used to implement steps that are common between the entire set of classes (e.g., launching a piece of software to be tested and getting it to a certain stage). The principle of inheritance simplifies management of the test software when, for example, the base class is modified, all of the tests which derive from that test case automatically are modified. Accordingly, only one item needs to be modified (instead of every tests) when a change is necessary to modify the way the software launches.

Abstract: Software (such as server products) operating in a complex networked environment often run on multi-machine installations that are known as machine clusters. A server product can be tested on a server machine type. The server product can be tested by tracking the constituent machines of a machine cluster, and configuring and recording the roles that each machine in the machine cluster plays. Scenarios targeting a single server machine-type can be seamlessly mapped from the single machine scenario to a machine cluster of any number of machines, while handling actions such as executing tests and gathering log files from all machines of a machine cluster as a unit.

Abstract: Smart test attributes are objects that are arranged to incorporate attributes functionality in the attributes themselves and to provide a standard way to interact with the attributes through a set of interfaces. The set of interfaces includes interfaces for class level attributes, method level attributes, and parameter level attributes. Test class attributes can be used to modify an instantiated object state, skip test extraction from a class, or cause test extraction to be performed multiple times for a denoted type. Method level attributes are capable of modifying method parameters and method execution. In an embodiment, method level attributes include execution attributes and supplemental attributes. Parameter level attributes are optionally used to modify the parameter input to a method and/or to modify a state of an object (e.g., the context) after a method has executed.

Abstract: Test software on a test client dynamically locates necessary files by replacing indirect file references in test code with actual file paths. File paths are determined using one or more root paths couple with one or more test parameters being used as a portion of the actual file path. Multiple root paths may be provided in a prioritized list, such that if a file is not found in a first location, additional locations are checked. Test software on a test controller receives a command to perform a test run and queries a data store for test information. A message is assembled using query results and delivered to one or more test clients for execution.

Abstract: A test method executor is an object designed to execute a test method. The test method executor typically implements a simple state engine that is used to process the data presented by each smart test attribute. The test method executor invokes particular test methods in response to the processed data. The test method executor then condenses the results from all the attributes typically into a simple return value, which is designed to be interpreted by the test harness. The return value indicates, for example, whether the executed test method was a success, failure, or if the test method was “skipped.” Additionally, the test method executor is used to gather data about the method being invoked (such as the method name, which attributes are present, and the like.

Abstract: A test services provider is an object that is arranged to provide a standardized interface for calling test harness provided functionality. The test services provider is not tied to a specific test harness, and provides a standard interface such that both test harness functionality and test cases can be written without beforehand knowledge of the other. In operation, the test harness registers the test services that provides with the test service provider, and the test cases retrieve the registered test services from the test harness as needed. Accordingly, the test case does not have to query the test harness itself for the object that provides the desired test harness functionality, but rather uses a standardized interface provided by the test services provider to retrieve the desired test services.