Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/thetonymaster/test_framework
https://github.com/thetonymaster/test_framework
Last synced: 18 days ago
JSON representation
- Host: GitHub
- URL: https://github.com/thetonymaster/test_framework
- Owner: thetonymaster
- License: apache-2.0
- Created: 2017-06-20T02:56:59.000Z (over 7 years ago)
- Default Branch: master
- Last Pushed: 2017-08-01T21:43:26.000Z (over 7 years ago)
- Last Synced: 2024-10-21T19:34:28.282Z (2 months ago)
- Language: Groovy
- Size: 8.14 MB
- Stars: 1
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE.md
Awesome Lists containing this project
README
# Cartridge Skeleton
The purpose of this repository is to define a base cartridge with empty job definitions and pipelines to allow developers to rapidly develop their cartridges.
## Stucture
A cartridge is broken down into the following sections:
* infra
* For infrastructure-related items
* jenkins
* For Jenkins-related items
* src
* For source control-related items
## Metadata
Each cartridge should contain a "metadata.cartridge" file that specifies the following metadata:
* `CARTRIDGE_SDK_VERSION`
* This defines the version of the Cartridge SDK that the cartridge conforms to
## Using this Repository
When developing a cartridge it is advisable to make a copy of this repository and remove all of the README.md files so that it serves as a basis for the new cartridge.
# Test framework configuration file (draft)
## Container configuration options
- `limit`: maximum number of containers that can be deployed
- `memory`: how much memory the containers can take
Example:
````yaml
containers:
limit: 10
memory: 512mb
````
## Tests
- `framework`: the framework used to run the tests, example JUnit, Codepcetp, etc.
- `repo`: the repo where the tests are stored
- `args`: some extra arguments needed to run the tests
Example:
````yaml
junit:
- repo: ssh://[email protected]
````
## Options
Options related to how the framework will behave and execute different tasks
- `time`: maximum time the framework should wait before starting new containers
- `priority`: which tests the framework should prioritize
- `processor`: the percentage the process should wait before splitting tests
- `memory`: how much memory the tests should consume before deploying new containers
Example:
````yaml
time: 3m
priority: time_consuming
````
## Sample file
````yaml
---
configuration:
containers:
limit: 10
memory: 512mb
tests:
junit:
- repo: ssh://[email protected]
codecetp:
- repo: ssh://[email protected]
options:
time: 3m
priority: time_consuming
processor: 30
````