# Automation Kit Repository
Welcome to the Automation Kit repository!
*Note:* This package is progressing quickly but is not yet ready for full production environments.
# Description
The **Automation Kit** is a python toolkit for building distributed automated task and testing systems. It goes beyond the capabilities of other task and test automation frameworks by providing a hybrid approach that allows for dependency injection, similar to pytest, combined with and object oriented framework that can be utilized to easily customize the orchestration of tasks and tests across a collection of integrated resources. Because the **Automation Kit** is built from the start with distributed automation in mind, it can help you quickly get distributed automated systems up and running that are based on a tested and proven set of object patterns and APIs.
# Design Philosophies
This section covers some of the important design features of the **Automation Kit** framework.
## Large Scale
The **Automation Kit** is designed for enterprise level distributed automation *"at scale"*. The term *"at scale"* refers not only to a larger collection of enterprise resources but also refers to the fact that the **Automation Kit** helps to setup patterns that will support working in a very large code base. The size of a code base that you might see associated with large enterprise level projects. The **Automation Kit** supports working in large code bases by helping to establish good code organizational patterns and abstractions that support characteristics that:
* make it easier to learn and work in the code base
* make the code base easier to maintain
* make it easier to share and reuse code
## Faster Classification of Issues
One of the key philosophies behind the **Automation Kit** design is one of being able quickly and efficiently identify the nature of issues that come up during automation runs. The **Automation Kit** initially classifies errors into one of four categories:
* **Configuration** - We identify configuration issues quickly and classify them so as to ensure that resources are not waisted troubleshooting configuration related issues and that eronious test results or noise is not generated due to configuration related issues. We also want automation runs to fail out quickly if the automation configuration is not setup correctly, before waisting additional testing resources.
* **Environment** - The **Automation Kit** performs an initial diagnostic scan of the automation landscape and all the resources declared to be necessary to run a series of tasks or tests in order to provide indications of environmental failures as early as possible. This is important to ensure that we do not generate noise in automation results that are not related to the automation tasks or tests that might fail. Just as with configuration, we want automation runs to fail out quickly if the automation environment is not setup correctly.
* **Error** - The **Automation Kit** classifies un-expected errors, or errors that are not founded in an expectation of a result, as an **Error** condition. This helps to ensure these errors are given an appropriate initial direction or indication that the issues is a problem in the automation code and not an issue in the code that is the target of the automation run.
* **Failure** - The **AutomationKit** classifies failures that are associated with an expectation of behavior from a target under test as failures. This allows for the proper initial classification of an issue as being a problem that is likely a failure in the code being targeted by the automation and the behavior or result it should have exhibited.
Having the initial classification of issues fall into one of these four categories helps to ensure that issues are easier to triage and assign to the appropriate party for investigation and resolution. It also helps to establish categories that can be used for data collection in order to better analyse the performance of test infrastructure, test code and product code.
## Integration and Distributed Automation Support
The **Automation Kit** comes with enterprise level integration and distributed automation capabilities. The framework utilizes a customize-able set of classes that guides enterprise users through a process of creating a very robust integration object model based on the roles that enterprise resources play in an automation landscape.
The declaration of a custom automation landscape is as simple as setting an environment variable or passing a command line flag declaring the python module that contains a custom landscape derived class. The *Landscape* and *LandscapeDescription* derived classes work together to provide the **Automation Kit** with a description of the customized roles and integration mixin(s) that provide the connection between the tasks and test automation code.
## Task and Test Integration Declaration and Assurance
The **Automation Kit** utilizes its object model to allow tasks and tests to provide information about their associated integration points and scopes of execution to the automation framework. This integration declaration mechanism allows the automation framework to provide an early scan of the integration pathways and provide levels of assurance as to the stability of the automation landscape early in the automation process. This is vitally important as it eliminates the waist and noise that are often associated with automation runs that are performed against an automation Landscape that has broken, mis-configured or missing resources.
## Automation Job, Scope and Flow Control
The **Automation Kit** allows enterprise users to organize and customize the ordering of automation scope engagements and the flow of an automation job. This provides the automation engineer the ability to control the engagement of automation scopes of execution and allows for optimal use of time and overlapping of scopes of execution in a test run.
# Table of Contents
1. [Automation Software Stack](http://automationmojo.com/static/automationkit/docs/usermanual/10-automation-software-stack.html)
2. [Getting Started](http://automationmojo.com/static/automationkit/docs/usermanual/20-getting-started.html)
3. [Automation Configuration](http://automationmojo.com/static/automationkit/docs/usermanual/30-automation-configuration.html)
1. [Landscape File](http://automationmojo.com/static/automationkit/docs/usermanual/31-landscape-file.html)
2. [Topology File](http://automationmojo.com/static/automationkit/docs/usermanual/32-topology-file.html)
2. [Runtime File](http://automationmojo.com/static/automationkit/docs/usermanual/33-runtime-file.html)
3. [Credentials File](http://automationmojo.com/static/automationkit/docs/usermanual/34-credentials-file.html)
4. [TestRun Sequencing](http://automationmojo.com/static/automationkit/docs/usermanual/40-testrun-sequencing.html)
1. [Integration Couplings](http://automationmojo.com/static/automationkit/docs/usermanual/41-integration-couplings.html)
2. [Scope Couplings](http://automationmojo.com/static/automationkit/docs/usermanual/42-scope-couplings.html)
5. [Functional Description](http://automationmojo.com/static/automationkit/docs/usermanual/50-functional-description.html)
1. [Activation and Startup](http://automationmojo.com/static/automationkit/docs/usermanual/51-activation-and-startup.html)
2. [Inter-Operability](http://automationmojo.com/static/automationkit/docs/usermanual/52-inter-operability.html)
3. [SSH Coordinator and Agent](http://automationmojo.com/static/automationkit/docs/usermanual/53-ssh-coordinator-and-agent.html)
4. [UPNP Coordinator and Agent](http://automationmojo.com/static/automationkit/docs/usermanual/54-upnp-coordinator-and-agent.html)
6. [Workflow Orchestration](http://automationmojo.com/static/automationkit/docs/usermanual/60-workflow-orchestration.html)
7. [Enterprise Extensibility](http://automationmojo.com/static/automationkit/docs/usermanual/70-enterprise-extensibility.html)
8. [Command Line](http://automationmojo.com/static/automationkit/docs/usermanual/80-command-line.html)
9. [Code Organization and Conventions](http://automationmojo.com/static/automationkit/docs/usermanual/90-code-organization-and-conventions.html)
10. [Coding Standards](http://automationmojo.com/static/automationkit/docs/usermanual/100-coding-standards.html)
Raw data
{
"_id": null,
"home_page": "",
"name": "automationkit",
"maintainer": "",
"docs_url": null,
"requires_python": ">=3.8,<4.0",
"maintainer_email": "",
"keywords": "automation,continuous-integration,distributed-test-framework,distributed-testing-tools,distributed-testing,upnp,test-automation,test-framework,testing,testing-tools",
"author": "Myron Walker",
"author_email": "myron.walker@gmail.com",
"download_url": "https://files.pythonhosted.org/packages/30/93/f0a9df7e232528a4bd9e22b2eb67ab31888d96f29f86ba08424d1a389cf0/automationkit-0.5.1.tar.gz",
"platform": null,
"description": "# Automation Kit Repository\n\nWelcome to the Automation Kit repository!\n\n\n*Note:* This package is progressing quickly but is not yet ready for full production environments.\n\n# Description\nThe **Automation Kit** is a python toolkit for building distributed automated task and testing systems. It goes beyond the capabilities of other task and test automation frameworks by providing a hybrid approach that allows for dependency injection, similar to pytest, combined with and object oriented framework that can be utilized to easily customize the orchestration of tasks and tests across a collection of integrated resources. Because the **Automation Kit** is built from the start with distributed automation in mind, it can help you quickly get distributed automated systems up and running that are based on a tested and proven set of object patterns and APIs.\n\n# Design Philosophies\nThis section covers some of the important design features of the **Automation Kit** framework.\n\n## Large Scale\nThe **Automation Kit** is designed for enterprise level distributed automation *\"at scale\"*. The term *\"at scale\"* refers not only to a larger collection of enterprise resources but also refers to the fact that the **Automation Kit** helps to setup patterns that will support working in a very large code base. The size of a code base that you might see associated with large enterprise level projects. The **Automation Kit** supports working in large code bases by helping to establish good code organizational patterns and abstractions that support characteristics that:\n\n* make it easier to learn and work in the code base\n* make the code base easier to maintain\n* make it easier to share and reuse code\n\n## Faster Classification of Issues\nOne of the key philosophies behind the **Automation Kit** design is one of being able quickly and efficiently identify the nature of issues that come up during automation runs. The **Automation Kit** initially classifies errors into one of four categories:\n\n* **Configuration** - We identify configuration issues quickly and classify them so as to ensure that resources are not waisted troubleshooting configuration related issues and that eronious test results or noise is not generated due to configuration related issues. We also want automation runs to fail out quickly if the automation configuration is not setup correctly, before waisting additional testing resources.\n* **Environment** - The **Automation Kit** performs an initial diagnostic scan of the automation landscape and all the resources declared to be necessary to run a series of tasks or tests in order to provide indications of environmental failures as early as possible. This is important to ensure that we do not generate noise in automation results that are not related to the automation tasks or tests that might fail. Just as with configuration, we want automation runs to fail out quickly if the automation environment is not setup correctly.\n* **Error** - The **Automation Kit** classifies un-expected errors, or errors that are not founded in an expectation of a result, as an **Error** condition. This helps to ensure these errors are given an appropriate initial direction or indication that the issues is a problem in the automation code and not an issue in the code that is the target of the automation run.\n* **Failure** - The **AutomationKit** classifies failures that are associated with an expectation of behavior from a target under test as failures. This allows for the proper initial classification of an issue as being a problem that is likely a failure in the code being targeted by the automation and the behavior or result it should have exhibited.\n\nHaving the initial classification of issues fall into one of these four categories helps to ensure that issues are easier to triage and assign to the appropriate party for investigation and resolution. It also helps to establish categories that can be used for data collection in order to better analyse the performance of test infrastructure, test code and product code.\n\n## Integration and Distributed Automation Support\nThe **Automation Kit** comes with enterprise level integration and distributed automation capabilities. The framework utilizes a customize-able set of classes that guides enterprise users through a process of creating a very robust integration object model based on the roles that enterprise resources play in an automation landscape.\n\nThe declaration of a custom automation landscape is as simple as setting an environment variable or passing a command line flag declaring the python module that contains a custom landscape derived class. The *Landscape* and *LandscapeDescription* derived classes work together to provide the **Automation Kit** with a description of the customized roles and integration mixin(s) that provide the connection between the tasks and test automation code.\n\n## Task and Test Integration Declaration and Assurance\nThe **Automation Kit** utilizes its object model to allow tasks and tests to provide information about their associated integration points and scopes of execution to the automation framework. This integration declaration mechanism allows the automation framework to provide an early scan of the integration pathways and provide levels of assurance as to the stability of the automation landscape early in the automation process. This is vitally important as it eliminates the waist and noise that are often associated with automation runs that are performed against an automation Landscape that has broken, mis-configured or missing resources.\n\n## Automation Job, Scope and Flow Control \nThe **Automation Kit** allows enterprise users to organize and customize the ordering of automation scope engagements and the flow of an automation job. This provides the automation engineer the ability to control the engagement of automation scopes of execution and allows for optimal use of time and overlapping of scopes of execution in a test run.\n\n# Table of Contents\n1. [Automation Software Stack](http://automationmojo.com/static/automationkit/docs/usermanual/10-automation-software-stack.html)\n2. [Getting Started](http://automationmojo.com/static/automationkit/docs/usermanual/20-getting-started.html)\n3. [Automation Configuration](http://automationmojo.com/static/automationkit/docs/usermanual/30-automation-configuration.html)\n 1. [Landscape File](http://automationmojo.com/static/automationkit/docs/usermanual/31-landscape-file.html)\n 2. [Topology File](http://automationmojo.com/static/automationkit/docs/usermanual/32-topology-file.html)\n 2. [Runtime File](http://automationmojo.com/static/automationkit/docs/usermanual/33-runtime-file.html)\n 3. [Credentials File](http://automationmojo.com/static/automationkit/docs/usermanual/34-credentials-file.html)\n4. [TestRun Sequencing](http://automationmojo.com/static/automationkit/docs/usermanual/40-testrun-sequencing.html)\n 1. [Integration Couplings](http://automationmojo.com/static/automationkit/docs/usermanual/41-integration-couplings.html)\n 2. [Scope Couplings](http://automationmojo.com/static/automationkit/docs/usermanual/42-scope-couplings.html)\n5. [Functional Description](http://automationmojo.com/static/automationkit/docs/usermanual/50-functional-description.html)\n 1. [Activation and Startup](http://automationmojo.com/static/automationkit/docs/usermanual/51-activation-and-startup.html)\n 2. [Inter-Operability](http://automationmojo.com/static/automationkit/docs/usermanual/52-inter-operability.html)\n 3. [SSH Coordinator and Agent](http://automationmojo.com/static/automationkit/docs/usermanual/53-ssh-coordinator-and-agent.html)\n 4. [UPNP Coordinator and Agent](http://automationmojo.com/static/automationkit/docs/usermanual/54-upnp-coordinator-and-agent.html)\n6. [Workflow Orchestration](http://automationmojo.com/static/automationkit/docs/usermanual/60-workflow-orchestration.html)\n7. [Enterprise Extensibility](http://automationmojo.com/static/automationkit/docs/usermanual/70-enterprise-extensibility.html)\n8. [Command Line](http://automationmojo.com/static/automationkit/docs/usermanual/80-command-line.html)\n9. [Code Organization and Conventions](http://automationmojo.com/static/automationkit/docs/usermanual/90-code-organization-and-conventions.html)\n10. [Coding Standards](http://automationmojo.com/static/automationkit/docs/usermanual/100-coding-standards.html)\n",
"bugtrack_url": null,
"license": "LICENSE.txt",
"summary": "Automation Kit Test Framework",
"version": "0.5.1",
"split_keywords": [
"automation",
"continuous-integration",
"distributed-test-framework",
"distributed-testing-tools",
"distributed-testing",
"upnp",
"test-automation",
"test-framework",
"testing",
"testing-tools"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "9d6fc5bacdf44e15cf1fe5d631dd5e81467abb3fbfd353977364fe874834bbdd",
"md5": "bfee6fb0ec3ebf549584e736933e1f30",
"sha256": "739234a584da4f61e7c72ade12867a59a7e21d43617a874fc5474362d2e1667f"
},
"downloads": -1,
"filename": "automationkit-0.5.1-py3-none-any.whl",
"has_sig": false,
"md5_digest": "bfee6fb0ec3ebf549584e736933e1f30",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.8,<4.0",
"size": 760687,
"upload_time": "2023-04-19T05:46:54",
"upload_time_iso_8601": "2023-04-19T05:46:54.893291Z",
"url": "https://files.pythonhosted.org/packages/9d/6f/c5bacdf44e15cf1fe5d631dd5e81467abb3fbfd353977364fe874834bbdd/automationkit-0.5.1-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "3093f0a9df7e232528a4bd9e22b2eb67ab31888d96f29f86ba08424d1a389cf0",
"md5": "df330d7a13e901fc6574a82315b488b1",
"sha256": "4d0affb0c798275bf080cc64836cc69458773459ca7db8908dd9338d026b8c64"
},
"downloads": -1,
"filename": "automationkit-0.5.1.tar.gz",
"has_sig": false,
"md5_digest": "df330d7a13e901fc6574a82315b488b1",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.8,<4.0",
"size": 421656,
"upload_time": "2023-04-19T05:46:57",
"upload_time_iso_8601": "2023-04-19T05:46:57.823721Z",
"url": "https://files.pythonhosted.org/packages/30/93/f0a9df7e232528a4bd9e22b2eb67ab31888d96f29f86ba08424d1a389cf0/automationkit-0.5.1.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2023-04-19 05:46:57",
"github": false,
"gitlab": false,
"bitbucket": false,
"lcname": "automationkit"
}
JSON