-
Notifications
You must be signed in to change notification settings - Fork 23
Development Tools
matt-primrose edited this page Aug 16, 2023
·
1 revision
- Docker: Used to build, test, and deploy applications. Containers have everything a software needs to run like libraries, tools, etc.
- Kubernetes: Used for automating software deployment, scaling, and management
- JavaScript library
- Models states in applications (state management scenarios)
- Components include states, events, transitions, hierarchical states, side effects, and visualization/debugging
- Creates the opportunity to implement better code as these components help paint a strong picture of how the system will be operating in it's various different aspects
- Also a JavaScript library
- Works in handling asynchronous events, system event manipulations, data, and real time applications
- It is another way to help create more refined code as it offers a way to better understand complex events that may take place within a system
- Main development section is the src drop down, most files regarding development will be there
- Unique section of files is the amt category which deals with http handling, CIRA connections, and device connection
- Main development section is the src drop down, most files regarding development will be there
- Unique section of files is the stateMachine category which deals with state machine activation, CIRA connections, amt passwords, networks, maintenance, errors, tls, wired and wireless functionalities, and more
- RPC-Go is the version that is now supported over the original RPC-C. We have refactored the old RPC from C to Golang
- The tool allows for API testing which allows us to test to see if we are generating the right responses from the specific API calls (GET, POST, DELETE). Open amt cloud toolkit's mps and rps both have a folders called "src", within them there is a "test" folder, and within that folder there is another subfolder called "collections". Here there is a collections.json file and a envionment.json file that can be imported into Postman to conduct the API tests.
- If you have access to the repo a good first step is to check it out (Private): https://github.com/open-amt-cloud-toolkit/e2e-testing
- This is for the nightly automated E2E tests
- To run an E2E test check out the repo, click on Actions on the top toolbar, then on the left hand side of the screen click on OpenAMT E2E, then hit the drop down Run Workflow and select the branch which you want to build and test
- There are certain machines that have ACM and CCM pipelines that automate builds from different branches to ensure that the toolkit still operates properly
- There are several .yml which help control the automation and flow of the E2E tests
- Umbrella term for anything done in an automated fashion (Continuous Integration). Continuous Deployment the integrated material into production environment
- Debug Environment Setup (DebugEnvironmentSetup.md)