Skip to content

mecuai/mecuai

Repository files navigation

MecuAI Core Latest v1.2.6.8

CI master develop

MecuAI Connect with MecuAI

Through the MecuAI ecosystem that lets users mine, buy and sell MECU securely and efficiently.

MECUAI is a decentralized network that connects blockchains, similar to how the internet connects computers.

With MECUAI, you can mine. You can run your own smartnodes, and you can buy and sell your MECU to others.

MecuAI Revolutionary PoW and PoS Layer-1 Blockchain

License

MecuAI Core is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.

Development Process

The master branch is meant to be stable. Development is done in separate branches. Tags are created to indicate new official, stable release versions of MecuAI Core.

The contribution workflow is described in CONTRIBUTING.md.

Testing

Testing and code review is the bottleneck for development; we get more pull requests than we can review and test on short notice. Please be patient and help out by testing other people's pull requests, and remember this is a security-critical project where any mistake might cost people lots of money.

Automated Testing

Developers are strongly encouraged to write unit tests for new code, and to submit new unit tests for old code. Unit tests can be compiled and run (assuming they weren't disabled in configure) with: make check. Further details on running and extending unit tests can be found in /src/test/README.md.

There are also regression and integration tests, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: test/functional/test_runner.py

The Travis CI system makes sure that every pull request is built for Windows, Linux, and OS X, and that unit/sanity tests are run automatically.

Manual Quality Assurance (QA) Testing

Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.