Home      |       About Us      |       NAVY 311 Services      |       Metrics      |       Resources      |       NAVY 311 FAQs      |       NIAPS Welecome to the NAVY 311 website!  Click a link on the gray navigation bar to view other sections of this site.

NIAPS Frequently Asked Questions (FAQs)

FAQ Categories

 

NIAPS Basics

Joining NIAPS

NIAPS Replication

NIAPS Testing

NIAPS Training

NIAPS Contacts


Can't find an FAQ for your question? Contact:
Navy311@navy.mil.

NIAPS Testing

Will my product go through testing prior to going out on a NIAPS release?

Yes. All products that will be part of a NIAPS version release will go through testing.          Back to Top


What kinds of testing will my product go through?

There are several kinds of testing a product may go through. They include:

  • Installation testing - This is a single application test. The installation test verifies that the product will properly install onto the server that NIAPS resides on. The testing occurs on a test NIAPS server that has the proper build for the NIAPS version the product is targeted to be rolled out on. Installation testing verifies log files, installation paths, any connection to databases, proper users and groups, proper permissions as well as a launch of the product. During this testing phase, the NIAPS test team may ask for installation test cases to aid with this kind of testing.
  • Functional testing - This is a single application test. The functional test verifies that the product functions as it is designed to based on a product owner supplied user guide. This testing occurs on a test NIAPS server that has the proper build for the NIAPS version the product is targeted to be rolled out on. Functional testing is usually accompanied by product owner supplied test cases that are performed by the NIAPS test team. The tester will act as a user at both the server and workstation level and will attempt to perform all the "daily" functions a typical user would perform as defined in the product's user guide. The functional test results in a pass/fail decision. Errors discovered during this testing phase are normally worked out with the product owner while it is in this testing phase. If a failure occurs BEFORE the NIAPS code lockdown milestone, a Remedy trouble ticket is created and the NIAPS test team contacts the product owner. Once the issue is resolved, testing is resumed. If the failure (a failure other than a minor bug fix) occurs AFTER the NIAPS code lockdown milestone, the product release is pushed back until the next available NIAPS release. During this testing phase, the NIAPS test team may ask for functional test cases to aid with this kind of testing.
  • Deployment testing - This is a test of all the products together that will be going out on a particular NIAPS release. Only the products that pass functional testing are tested during this phase. The installers of all the "passed" applications are put onto a NIAPS publisher. A batch file is then created and each product's installer is run. Once this has been completed, an amendment of all the installers are put into a batch file and pushed out to a test server where the batch file is run to test all product installers.
  • Replication testing - Only products that have replication requirements (i.e. moving data from shore to ship, ship to shore, or both) will be tested during this phase. Like the deployment testing, this test process tests all the products that have passed functional testing. This test simulates the shipboard replication processes of moving data from ship to shore and from shore to ship. The test ensures the product can receive data properly and output data in the right directions. During this testing phase, the NIAPS test team may ask for replication test cases to aid with this kind of testing.
  • Regression (Integration) testing - This is a test of all the products together that will be going out on a particular NIAPS release. The testing occurs on a test NIAPS server that has the proper build for the NIAPS version the product is targeted to be rolled out on. This testing phase ensures the products that will be going out on a NIAPS release together all interact well with each other. This test is always done after replication testing, after the release of any server security patch or any other major change to the server NIAPS is residing on.

Back to Top


Can my product be tested on a particular ship platform before releasing it to more than one ship?

Yes. This is an option. The NIAPS Configuration Management Team will arrange telecoms with the NIAPS Certification and Accreditation Team and NIAPS Testing Team to discuss specific requirements.          Back to Top


Can I get access to a NIAPS test server?

This is an option. Current testing environment options include:

  • Direct Connect Online (DCO) - Similar to Microsoft Net-Meeting, this method is a light web-based client that allows users to see the testing occurring and allows users to "take control" of the server. This method is accessible only during NSWC Crane Distance Support Innovation Lab (DSIL) office hours and there must be DSIL team members present during the testing session(s).
  • Remote desktop/CITRIX - This method requires the submission of a System Access Authorization Request (SAAR) first before it can be used. Requesting a SAAR for this option is done through the NIAPS Configuration Manager at NSWC Crane. This method will consist of logging into Citrix and using remote desk top functionality to access a DS Server that is located within the DSIL at NSWC Crane. Availability to a specific test server is limited and access is given at the DSIL's discretion. Scheduling the use of a test server first begins by contacting the NIAPS Configuration Management (CM) Lead at 812-854-3604. The NIAPS CM Lead will then walk you through the process of getting access. Once access is granted, testers will have the ability to test 24/7 during scheduled availability.
  • Virtual Machines - This method provides wider availability for access than the two previous mentioned options. Testing will actually take place on official DS NIAPS configurations. Scheduling the use of a virtual machine will first begin by contacting the NIAPS CM Lead at 812-854-3604. The NIAPS CM Lead will then walk you through the submission of a NIAPS Server Request (NSR) which is submitted via the NIAPS Dimensions CM tool. Once VM usage is approved and access is granted, testers will have the ability to test 24/7 during scheduled availability.

The NIAPS CM Lead will arrange any telecoms needed with the NIAPS Certification and Accreditation Team and and NIAPS Testing Team to discuss specific requirements.          Back to Top

 

Quick Links

No Fear Act   |   FOIA   |   Security & Privacy
Accessibility/Section 508   |   Fraud, Waste & Abuse
Suicide Prevention   |   Navy Jobs   |   USA.gov

This is an official United States Navy Website.

Contact Webmaster   |   Site Map
This US Government system is subject to monitoring. Please review the Privacy Policy.

The appearance of external hyperlinks does not constitute endorsement by the United States Department of Defense, the United States Department of the Navy and the Space and Naval Warfare Systems Command (SPAWAR) of the linked web sites, or the information, products or services contained therein. For other than authorized activities such as military exchanges and Morale, Welfare and Recreation (MWR) sites, the United States Department of Defense, the Department of the Navy and the Space and Naval Warfare Systems Command does not exercise any editorial control over the information you may find at these locations. Such links are provided consistent with the stated purpose of this DoD web site.

In order to provide our customers with the best information more effectively, the SPAWAR Enterprise Public Website has undergone several recent revisions. We welcome your comments regarding revisions or other issues.  Please send us your feedback.