Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/tokenika/eosfactory

Python-based EOS smart-contract development & testing framework
https://github.com/tokenika/eosfactory

eos python smart-contracts testnet unit-testing

Last synced: about 1 month ago
JSON representation

Python-based EOS smart-contract development & testing framework

Awesome Lists containing this project

README 

        
# Welcome to EOSFactory v3.4.0



[EOSFactory](http://eosfactory.io/) is a Python-based [EOS](https://eos.io) smart-contract development & testing framework, created by [Tokenika](https://tokenika.io).



With a single command-line interface you can create a private testnet and then compile, test and deploy EOS smart-contracts.



All of this using simple yet powerful [Python3](https://www.python.org/) syntax.



## Why it’s needed?



Code development and testing involve tasks that need to be executed hundreds of times, and each time in exactly the same way and exactly the same context. Therefore those tasks need to be fully automated, as otherwise a lot of time is being wasted and, what’s even worse, a lot of additional uncertainty is introduced. Manually performed actions are prone to errors.



And this is what *EOSFactory* actually brings to the table: an easy & intuitive way to automate the process of dealing with smart-contracts. Write down, in the form of a Python script, what needs to be done multiple times in exactly the same way and exactly the same context, and then just run the script. *EOSFactory* will take care of everything else: it will compile your smart-contract, create a new local testnet, deploy the contract, invoke its methods and verify the response, then tear down the testnet, and finally report the results. And all of this done in a couple of seconds.



## Main features



#### 1. Object-oriented



When you use tools like `cleos` all you have at your disposal is issuing separate, one-off commands, as `cleos` is not able to keep your state. Thus each time you interact with a contract, you need to tell `cleos` which contract and which account you mean. Contrary to that, in *EOSFactory* everything is an object. You create a contract (or an account), keep reference to it and then invoke its various methods.



#### 2. Simple syntax



The front-end of *EOSFactory* is simply a Python3 *Command Line Interface*. This way you can interact with EOS smart-contract, and prove it works as expected, instead having to deal with the raw primitives of the EOSIO `cleos`. In most cases Python syntax is immediately clear for everyone.



#### 3. Support for both local and remote testnet



Running tests on a public testnet is much more complex than using a local one where you have full control. The whole infrastructure of *EOSFactory* is designed in such a way that the same test is able to work in both environments, and switching between them is just a matter of changing one parameter.



#### 4. Aliases for account names



*EOSIO* accounts are indexed by their names, thus those names have to be unique within the blockchain namespace and have to follow specific restrictions. As a result, most of the human readable combinations are already taken, even in a testnet environment. *EOSFactory* hides the actual names of an *EOSIO* accounts behind a system of human-friendly aliases.



#### 5. Truly cross-platform



We make sure everything we do is fully compatible with Windows - our toolset enables you to run an EOS node and interact with it on any operating system, including Windows, MacOS and Linux.



## User documentation



* [Introduction to EOSFactory](docs/tutorials/00.IntroductionToEOSFactory.md)

* [Installing EOSFactory](docs/tutorials/01.InstallingEOSFactory.md)

* [Interacting with EOS Contracts in EOSFactory](docs/tutorials/02.InteractingWithEOSContractsInEOSFactory.md)

* [Building and Deploying EOS Smart-Contracts in EOSFactory](docs/tutorials/03.BuildingAndDeployingEOSContractsInEOSFactory.md)

* [Working with EOS Smart-Contracts Using EOSFactory in VSC](docs/tutorials/04.WorkingWithEOSContractsUsingEOSFactoryInVSC.md)

* [Interacting with Public Testnets](docs/tutorials/05.InteractingWithPublicTestnet.md)

* [Using EOSFactory with an Existing EOS Smart-Contract Project](docs/tutorials/06.UsingEOSFactoryWithExistingProject.md)



## Use cases



* [Wallet Class](docs/cases/wallet.md)

* [Symbolic Names](docs/cases/symbolic_names.md)

* [Account Class](docs/cases/account.md)

* [Master Account](docs/cases/master_account.md)



## Complete documentation



Please refer to the [table of contents](https://eosfactory.io/build/html/index.html).



## Release notes



Please refer to [this document](docs/ReleaseNotes.md).



## Roadmap



Our long-term goal is to turn *EOSFactory* into a comprehensive IDE (Integrated Development Environment) for EOS smart-contracts.



- [Plan for Subsequent EOSFactory Releases](docs/roadmap/PlanForSubsequentEOSFactoryReleases.md)

- [Long-term EOSFactory Roadmap](docs/roadmap/LongTermEOSFactoryRoadmap.md)



## Support



For issues not covered in the documentation there is a dedicated [EOS Factory Support](https://t.me/EOSFactorySupport) channel on Telegram.



## Licence



This code is provided as is, under [MIT Licence](LICENCE).



Your question is not clear to me.

If you refer to the statement from the tutorial *InstallingEOSFactory*:



*EOSIO* deployed in Docker is NOT supported.*.



Here we communicate that *EOSIO* executable has to be installed in the system directly, and not as a Docker image.



We do not like Docker because WSL (Windows System Linux) does not support it. However, we can consider meeting demand from Linux System users, if we see such.