FLHSMV-RFI-036-22 - Automated Software App Testing.pdf

State of Florida Department of Highway Safety and Motor Vehicles

Request for Information (RFI) No.: FLHSMV-RFI-036-22 Automated Software Application Testing Solution

FLHSMV-RFI-036-22, Page 1 of 8

1.0 INTRODUCTION

The State of Florida, Department of Highway Safety and Motor Vehicles (hereinafter “FLHSMV” or “Department”), Office of Motorist Modernization (“OMM” or “Office”), issues this Request for Information (RFI) seeking information from parties with proven, verifiable, and documented expertise concerning an automated software application testing solution (“application” or “solution”).

This is an RFI, as defined in section 287.012(22), Florida Statutes (F.S.), for planning purposes only. This is not a solicitation for offers. The information gathered from this RFI may be used to develop a future competitive solicitation.

Please monitor the MyFloridaMarketPlace Vendor Information Portal (VIP) for any changes or notices prior to submitting a response.

2.0 DEFINITIONS

A. Software and Application: A computer software package that performs a specific function directly for an end user or, in some cases, for another application. An application can be self-contained or a group of programs.

“Software” and “Application” may be used interchangeably.

B. Application Security Testing: The process of making applications more resistant to security threats, by identifying security weaknesses and vulnerabilities in source code.

C. Capacity Testing: A test to determine how many users the application can handle before either performance or stability becomes unacceptable.

D. DevOps Methodology: A set of practices that combines application development (Dev) and Information Technology (IT) Operations (Ops). It aims to shorten the systems development life cycle and provide continuous delivery with high application quality.

E. Feature Testing: Testing of any new feature added to software or any modification to an existing feature to determine if it functions as expected and has no flaws.

F. Infrastructure Performance Testing: The testing process that covers hardware, software, and networks. It involves testing any code that reads https://vendor.myfloridamarketplace.com/

FLHSMV-RFI-036-22, Page 2 of 8 configuration values from different things in the IT framework and compares them to intended results.

G. Integration Testing: Tests the integration of various units of functionality.

H. Load Testing: Type of software testing that is carried out to determine system performance in terms of sensitivity, reactivity, and stability under a particular workload.

I. Office: An organizational unit within a state agency or large unit. For purpose of this RFI, “Office” refers to Office of Motorist Modernization (OMM).

J. Performance Testing: Type of software testing which determines the performance of a system, software product, or software application under real life-based load conditions.

K. Pre-Production: The various staging environments that help developers safely develop, test, and integrate new code.

L. Regression Testing: Validates existing functionality continues to work as designed with new code.

M. Response: All information, documentation, and other materials submitted by the Vendor in response to this RFI.

N. Software Feature: The changes made in the system to add new functionality or modify the existing functionality.

O. Stress Testing: Software testing that verifies stability and reliability of software application.

P. Tool(s): A software testing application(s).

Q. Unit Testing: A software testing method that tests the smallest unit of functionality, a unit of code in isolation of other code, or other dependencies.

R. User Interface Testing: A testing technique used to identify the presence of defects in any software in which a user may come into contact.

S. Vendor: Any firm or person who submits a response to the Department regarding this RFI. Vendor, Contractor, and Respondent may be used interchangeably throughout the RFI.

FLHSMV-RFI-036-22, Page 3 of 8

T. Volume Testing: A type of software testing that verifies system performance with extensive data. It reflects the reaction of websites and applications to the increased volume of users or products in the databases.

3.0 PURPOSE OF AN RFI

Rule 60A-1.042, Florida Administrative Code (F.A.C.), provides that an agency may request information by issuing a written RFI. Agencies are authorized to use an RFI in circumstances including, but not limited to, determining whether or not to competitively procure a commodity or contractual service, determining what solicitation process to use for a particular need, or researching general, special, and/or technical specifications for a solicitation.

A Vendor’s response to an RFI is not an offer (Rule 60A-1.042, F.A.C) and the agency may not use the Vendor’s submission to justify a contract with that Vendor without otherwise complying with Chapter 287, Florida Statutes (F. S.).

Vendor responses to this RFI will be reviewed for informational purposes only and will not result in award of a contract.

Vendors submitting a response to an agency’s RFI are not prohibited from responding to any related subsequent solicitation. Vendors are not required to submit an RFI response to participate in any subsequent solicitation.

4.0 CALENDAR OF EVENTS

The table below contains the Calendar of Events for this RFI. Vendors should become familiar with the Calendar of Events as the dates and times may be subject to change. It is the Vendor’s responsibility to check the Vendor Information Portal (VIP) for any changes. All changes to the Calendar of Events will be through an addendum to the RFI. Vendors are responsible for submitting all required documentation by the dates and times indicated below (Eastern Time).

DATE TIME ACTIVITY

May 12, 2022 RFI is released on the VIP.

May 20, 2022 3:00 p.m. Questions due.

May 27, 2022 Anticipated answers to questions are released.

June 10, 2022 2:00 p.m. RFI responses due.

https://www.flrules.org/gateway/ruleNo.asp?id=60A-1.042 https://www.flrules.org/gateway/ruleNo.asp?id=60A-1.042 https://www.flsenate.gov/Laws/Statutes/2020/Chapter287

FLHSMV-RFI-036-22, Page 4 of 8

5.0 ADDENDA TO THE RFI

The Department will post any addenda to this RFI on the Florida Vendor Information Portal (VIP) at: https://vendor.myfloridamarketplace.com/

Each Vendor is responsible for monitoring the VIP for new or changing information.

6.0 QUESTIONS

Questions or requests for clarification regarding this RFI shall be submitted in writing to the Procurement Officer identified in Section 8.0, Procurement Officer, by the date and time specified in the Calendar of Events or as amended by the Department. Questions will not be answered via telephone. The Department anticipates posting answers to questions received on the VIP by the close of business on the date stated in Section 4.0, Calendar of Events.

7.0 BACKGROUND

The Department is transforming the delivery of new applications both in-house and to external stakeholders in a faster, more responsive way. All new applications must be tested during the varying stages of development and prior to going into production. Such testing includes, but is not limited to, the following:

Performance Testing:

• Capacity

• Infrastructure Performance

• Load

• Stress

• Volume

Functional Testing:

• Application Security

• Feature

• Integration

• Regression

• Unit

• User Interface

Currently, application testing relies heavily on manual testing by designated office staff. With approximately 200 application development projects encompassed in Online Registration and Identity Operating Network (ORION), the time constraints for application testing leave no capacity to add more tests to the current, manual process.

8.0 PROCUREMENT OFFICER

The Procurement Officer, acting on the behalf of the Department, is the sole point-of-contact regarding all matters relating to this RFI. All questions and requests for clarification are to be directed to:

Corina Chiorescu https://vendor.myfloridamarketplace.com/

FLHSMV-RFI-036-22, Page 5 of 8

Bureau of Purchasing and Contracts Florida Highway Safety and Motor Vehicles Telephone: 850-617-3176 E-mail: CorinaChiorescu@flhsmv.gov and Purchasing@flhsmv.gov

9.0 PROJECT GOALS

The goal of this project is to implement an application testing solution that is continuous, stable, and automated across mobile devices and multiple personal computer browsers. The testing solution must include functional and performance tests of applications and infrastructure.

The anticipated interaction of the testing solution is indicated in Figure 1 below:

Figure 1 – DevOps Testing Strategy

10.0 REQUESTED INFORMATION

The Department is requesting information from Vendors with direct experience developing implementation strategies, writing script(s), and utilizing solution tool(s) to introduce automated application testing that aligns with continuous testing as part of a DevOps Methodology.

All responses to this RFI must contain, at a minimum, the following information:

mailto:CorinaChiorescu@flhsmv.gov mailto:Purchasing@flhsmv.gov

FLHSMV-RFI-036-22, Page 6 of 8

Vendor Background

a) A brief summary of Respondent’s organization, its history and experience with information requested in this RFI.

b) Customer references for previous work with federal, state, local, or county government, to include but not be limited to the following information:

• Detailed description of work performed

• Company/Department name

• Name of contact person and their contact information (i.e., phone number, email address, USPS mail address)

Functionality

c) A description of the Respondent’s solution, approach, and recommendation(s) on an application testing solution that is continuous, stable, and automated.

This should include but is not limited to discovery, testing, implementation, and training plans. Each plan should indicate estimated length of time to complete.

d) A description of the standardized testing solution that covers approximately 200

Department projects, utilizing currently in-use tools (Figure 1), with the capability of executing multiple automated tests simultaneously over multiple, pre-production environments.

e) A description of the Vendor’s proven capabilities of testing applications, environments, and the delivery process at every stage of the application delivery pipeline.

f) A description of ways in which the Department can introduce automated testing to the Vendor’s existing continuous integration solution.

g) A description/recommendation of dedicated tool(s) for automated functional, performance, and security testing of application and IT infrastructure in pre-production environments. All tools recommended must have through-life support.

Implementation/Analytics

h) A description of ways in which the Vendor can work with the Department to write testing scripts, introduce automated testing, and reach a level of continuous testing maturity.

i) A description of the types of real-time feedbacks, metrics, and analytics the recommended solution would provide and in what format(s) that could be consumed by Department stakeholder groups.

FLHSMV-RFI-036-22, Page 7 of 8

j) A description of recommended staffing resources and training requirements to ensure the Department can maintain a mature automated testing program.

Cost Provide sample cost information that would apply to a solution as described in the RFI response, including but not limited to, the following:

1. Product or Line Item

2. Quantity Required – Number of each product/line item required. Sample cost per product or line item.

3. Sample Overall Initial Cost (Up to 5-years)

4. Sample Optional Renewal Term Cost (Up to 5-years)

5. License fees associated with the solution

NOTE: To preserve your company’s ability to bid on any future procurements related to this RFI, it is important to provide general pricing information only (i.e., competitive ranges, and variable impacting price, etc., not a specific price quote).

Additional Information The Department is open to receiving any additional information that would meet the requirements described in this RFI.

11.0 RESPONSE SUBMISSION INSTRUCTIONS

A. Response Submission

The Vendor shall submit:

1. An electronic version of the original RFI response (marked “Original”) and of the redacted version of the redacted RFI response (marked “Redacted”), if applicable (see, Section 12.0, Proprietary Information).

The application used to produce the electronic files must be Microsoft Word 2010 and/or Excel 2010 or later. These electronic files must be logically named and clearly labeled. The redacted version of the RFI response should be suitable for release to the public. Any confidential or trade secret information covered under section 812.081, F.S., should be either redacted or completely removed. The redacted RFI response shall be marked “REDACTED” and must contain a transmittal letter authorizing release of the redacted version of the RFI in the event the Department receives a public records request.

https://www.flsenate.gov/Laws/Statutes/2020/0812.081

FLHSMV-RFI-036-22, Page 8 of 8

*Please note: If a redacted copy is not provided, the Department will provide a copy of the original submittal upon any public records request.

B. Delivery of RFI Submittal

All RFI responses shall be submitted via EMAIL ONLY and addressed to the Procurement Officer identified in Section 8.0 - Procurement Officer and must be received by or before the date and time indicated in the Calendar of Events.

Vendors are advised to examine their RFI responses carefully and to ensure all requirements are met and that the RFI response is delivered no later than the time indicated in the Calendar of Events. Hardcopy/paper submissions will not be accepted.

Vendors shall submit the RFI response (one copy of each: ORIGINAL and REDACTED) via email to the Procurement Officer indicated in Section 8.0, Procurement Officer. The email shall contain the RFI number FLHSMV-RFI- 036-22 – OFFICIAL RFI and company name.

12.0 PROPRIETARY INFORMATION

Any portion of the submitted response which is asserted to be exempt from disclosure under Chapter 119, F. S., shall be clearly marked “exempt”, “confidential”, or “trade secret” (as applicable) and shall also contain the statutory basis for such claims on every page. In accordance with Section 119.075, F.S., pages containing trade secrets shall be marked “trade secret as defined in section 688.002, F. S.” Failure to segregate and identify such portions shall constitute a waiver of any claimed exemption and the Department will provide such records in response to public records requests without notifying the Vendor. Designating material simply as “proprietary” will not necessarily protect it from disclosure under Chapter 119, F. S.

13.0 VENDOR COSTS

Vendors are responsible for all costs associated with the preparation and submission of their Request for Information response including any site visit. The State of Florida, Department of Highway Safety and Motor Vehicles will not be responsible for any vendor-related costs associated with responding to this request.

https://www.flsenate.gov/Laws/Statutes/2020/Chapter119 https://www.flsenate.gov/Laws/Statutes/2020/0812.081 https://www.flsenate.gov/Laws/Statutes/2020/0812.081 https://www.flsenate.gov/Laws/Statutes/2020/Chapter119