This too is quite expensive from an infrastructure perspective, but makes your testing and automation efforts far easier and with quality critical in working with blockchain systems, it would be an investment that is well worth it. This is why I recommend trying to set up a private test environment, or one that closely resembles the public offering in every way except scale. If you’re trying to do this in a public blockchain setup, it could prove quite expensive and can remove some predictability from your testing effort, as you can’t easily just return the state of your individual blocks to where they're needed. It's true that the blockchain component was not responsible for much of this functionality and merely acted as a storage medium, but the majority of data in which these decisions were made was from the individual blocks themselves. This includes purchases and withdrawals, varying account types, histories, and balances, understanding different tax regulations, and how the system handled it. In the FinTech space where I’ve spent most of my career, this means trying to create enough samples of different transaction types to cover all the relevant permutations required. While some of the data rules are often easy to understand in most blockchain systems, the immutability of transaction on the technology simply means that there can be little margin for error and so it's something that testing teams cannot compromise on in terms of understanding their permutations ánd ensuring the coverage of their test data is sufficient. The next key challenge, which is similar to other forms of testing, lies in creating enough user specific data to ensure you can meet all the required use cases. Many more specialized testers have since gotten involved and many of the new frameworks (which are explored further on in this article) have solved some of these end-to-end challenges.
Many companies had great solutions in place to help them with their testing efforts, but most were created by developers and so while these different testing engines were effective at mocking and replicating aspects of blockchain functionality, the scope of understanding their end-to-end functionality was not established. Get a front-row seat to the future of IoT data infrastructure at EMQ. The world’s most scalable and reliable MQTT messaging platform for mission-critical IoT scenarios.
Permute high quality vs. keep quality how to#
When I started making sense of blockchain systems and how to approach testing them, part of the initial challenge was the limited scope of examples I can learn from and established frameworks in place. Given the relative newness of the technology, there is still very little in the way of formal best practices or testing tools around blockchain technology, though this is something that is rapidly changing with a lot of new up and coming frameworks in this area. In this article, I will talk about some of the key challenges faced by teams needing to test blockchain technology, while also providing solutions to meeting those challenges.
Permute high quality vs. keep quality software#
As developers and test engineers, we need to be prepared for those changes to better adapt to the new technology and allow for the continued development of software and products through it, without compromising on quality. With change however, comes the added risk of quality issues. In short, testing in the blockchain can make you a better tester.īlockchain is an emerging software architecture that has the potential to be a big disruptor in the industry.
Key focus areas for functional testing include working with block size, chain size, data transmission and block transactions, while performance and security remain priorities.
Though good test analysis is still required to build a quality blockchain product.
0 kommentar(er)
