As you may have already understood, Alyvix 3 is coming! ๐Ÿ™‚ Our R&D team has decided to organize three different kickoff meetings, in order to really show how Alyvix 3 will look like. The first one already took place. I want to keep you updated, sharing with you some insights and some changes that will take place in the next months – or already did.

 

Alyvix kickoff meeting – August

The first meeting had three main goals:

  • Showing Alyvix 2, starting from its core functionalities;
  • Explaining the main reasons that led to Alyvix 3;
  • Introducing some info about Alyvix 3.

… Showing Alyvix 2, starting from its core functionalities

Alyvix is able to measure the end-user experience, synthesizing end-user consuming applications. Briefly: we monitor transaction waiting times, caring about latencies of network applications and streamed applications, proprietary clients. In the following pictures, you can see a taste of Alyvix 2 design: 

This is the current output of Alyvix 2. I would like to underline that this is an HTML report and that it is possible to obtain it only with a monitoring solution. In fact, at present, Alyvix 2 needs an input from an active monitoring solution to run its test cases. If we consider NetEye, this is the output without the integration of the performance data in Grafana, e.g. 
In the following pictures instead, Alyvix product owner has represented how the solution works. You can see how the different “elements” of Alyvix interact with each other…..
…. And how they interact with a monitoring solution – in this case, NetEye.

… Explaining the main reasons that led to Alyvix 3

Alyvix 2 has some restrictions and we are going to list some of them – not all of them, everyone has dirty laundry ;):

  • No editable keyword name;
  • No duplicable keywords;
  • Multitype keywords;
  • No guided test case building;
  • No natural Alyvix GUI integration;
  • Test cases are not duplicable;
  • No standard output integration;
  • No test case scheduling;
  • Test cases can’t be auto distributed.

In addition to those restrictions, Alyvix is written in Python 2, a programming language that is going to die in 2020.

 

… Introducing some info about Alyvix 3

First, our R&D team rewrote Alyvix in Python 3. It was hard work… But it had to be done! Therefore, you’re probably wondering… How will Alyvix UX change? Well, many things are going to change… but we’ll spoil only some of them ๐Ÿ™‚ As you can see in the pictures, Alyvix will be composed of several parts:

  • EDITOR (designer, object and editor)
  • ROBOT AND ENGINE
  • SERVER
It will be extremely easy to build test cases. In fact, Alyvix will recognize by himself the objects on the screen. Moreover, keywords will be editable and duplicable. A very disruptive (and cool ;)) news is that test cases will be also duplicable! What does it mean? It means that there will be “standard” test cases that can be downloaded at any time. Once downloaded, that’s it! They can run and proactively monitor your website or your application. This is possible thanks to Alyvix Robot. In fact, test cases will become “documents”, which can be read by Alyvix Robot. Subsequently, the Robot runs them. Therefore, Alyvix 3 won’t need any monitoring system to run its test cases. It will be able to schedule test cases by himself! This change also means that there won’t be integration problems anymore. The monitoring system will only check Alyvix probes to understand how test cases are running. It will ask data, in order to use and integrate them in the dashboards. In the following pic, you can see the steps done. Alyvix designer and Engine are done. Alyvix Selector and Alyvix Robot are under development instead.
Francesco, Alyvix Product Owner, has kindly prepared a useful screencast. It shows some differences between Alyvix 2 and Alyvix 3. If you want to watch it, do not hesitate to contact us ๐Ÿ™‚ info@alyvix.com