Work session with Shannon. We worked on content for the testing and integration plans for fracture. Going over what has worked and what are plans are going forward. We may tweak it a bit, but here is what we came up with (first round).

/////

We started the original adilas core back in 2001. At that time, testing was only something that you did as you built the different pages and functionality. Back in the day, we had one primary developer and he was in charge of the system. As new developers were added to the mix, and as time has gone on, the need for better, more structured testing has become evident. This combination of naturally growing the code base and meeting client needs, has helped us pioneer a successful web-based application and service our clients for over 20+ years.

Sometime between 2018-2020, more testing was generally added to our process. We have developers who are doing unit testing, mocking data, performing database connections, load testing, and running deeper integration tests. That has been a good shift for us as a company. Our plan it to continue along those lines, and even increase our testing focus.

The adilas user base has been a huge asset. We offer such a unique product and each company/user uses it in so many different ways. This has helped us get very unique testing coverage based on users and their system usage. We have actually added over half of our features based on user input, feedback, requests, and ideas. We love that. We plan on continuing in that path as well and will actively seek user feedback and input.

Additional testing, will help stabilize and improve ease of use as we keep building. Here are a few ways that we will continue with testing and integration plans:

• Functional and characterization testing - what does it currently do
• Unit testing - what are the individual parts and pieces - functions and methods
• Integration testing - how does it work with the other parts of the system
• Versioning and code repositories - historically tracking changes and auto deploying code to production servers
• Documentation, help files, and SOP's (standard operating procedures)
• Other testing and integration plans