Play2Live: Development Testing 7/20/18
To create the Play2Live platform many different interface must inter-operate on a single concurrent platform. Blockchain tokens, streaming, game tournaments, viewers and more, all need to be combined in one place to provide a user-friendly interface.
All these complex operations have to be carried out to ensure that users receive a pleasant experience from working with the platform, while a quality assurance team works to make certain that everything runs smoothly. In house testing becomes a pivotal tool to provide quality control of the Play2Live platform.
Testing is one of the hardest and most interesting parts in software development. Testing is a layer that runs between the programmers and the end users. The testing process checks the operational capabilities of the promised functions and features, which are implemented by the programmers, as well as user scripts that the user will be run the first time they visit the platform (and maybe not the first time). Here you need an understanding of the development process, as well as the functioning of specific features, and you also need an infinite amount of imagination for custom scenarios. And the QA team has absolutely no shortage of that. This is where testing ends and quality assurance begins. All ensuing actions are carried out in strict accordance with the established processes, as well as under strict control. Each release is accompanied by certain “rites and ceremonies” or “dances with tambourines”, when the friendly development team performs manual tests, automated tests, log checking, server loading, access speed testing and much, much more in accordance with the processes that ensure end product quality. The quality assurance team plays a critical role in this process, since only they have the final say whether the process is completed. The deployment (installation of updates) is not the only process monitored by the team, as there are other processes that are no less important. They are just not that interesting to mention.
A separate point worthy of note is autotesting. This process allows avoiding routine work and provides quick results about the performance of the platform. The tests are written in the high-level Python programming language. This language includes a variety of tools for any type of testing. The most interesting type of automated testing is testing of the GUI. The Selenium bot is used for such testing procedures. These tests can be visualized in the browser window and they allow for a visual display of how quickly the bot taps various buttons and tabs, and checks results and displays reports. The actions that would have taken a user two hours to conduct can be carried out by Selenium in less than a minute. Less visual, but no less important are the load tests, integration tests, unit tests, code coverage tests and others. All these tests are regularly launched and allow development teams to identify any problems or bugs almost instantly. If a problem is found, the development team immediately starts remedial procedures under the watchful eyes of the quality assurance team. Thus, the platform is being perfected ad infinitum.
This is an important and unseen element of work carried out by the QA team. And the less noticeable are the shortcomings, the better the quality of work of the development team.