Patches, version upgrades and functional changes represent the life cycle of information systems. In order to keep a high level of quality, it is essential to launch test campaigns every time you intervene on the system to ensure non-regression, not only functional but also technical. The automation of these tests will necessarily bring added value to customers by improving quality and optimising resources.
So, can we conclude that all clients use automated testing? Based on FEKRA’s experience feedback, the answer is NO, especially for functional tests. That’s understandable.
Many tools exist today to perform technical tests, whether they are unit tests, load tests, acceptance tests, etc.
However, from a functional point of view, it is different: we can note a gap between clients’ functional expectations and existing solutions.
The main obstacle is transition: how to move from manual to automated tests, how can hundreds of scenarios written to be executed by a human be understandable and executable by a robot? That is the missing link today and, in this context, FEKRA has introduced its new automated testing tool: PROCENIUM.
Procenium is FEKRA’s tool to perform functional and
technical automated tests.
From a functional point of view, PROCENIUM is based on a specific logic for writing test scenarios. The logic is:
1 test scenario = 1 test case
In most manual scenarios today, the logic is:
1 test scenario = N test cases
What does it mean?
You need to use more ‘IF… THEN’… in a same scenario.
To make PROCENIUM efficient, you must think process when writing a test scenario. A process is a series of reusable actions in different scenarios.
The key factor of the process is its granularity. A well-designed process is a
a process implemented only once without any evolution of any kind in time and that can be used several times in different scenarios.
In order to be able to design these processes, different actors must be involved:
FEKRA |
---|
Test Analyst: Rephrases the scenario if necessary |
Developer: Implements processes |
Client |
---|
Business Analyst: writes the scenario |
Business: defines functional needs |
The collaboration between the client’s business analyst and Fekra’s test analyst and
Fekra’s test analyst is essential for process design and pooling of test scenarios.
If the processes were well designed, once deployed, the client could then create new test scenarios with no development, the only requirement would be to compose the processes.
Language | Java |
Test tool | Selenium web driver customised version |
Reporting tool | XML, HTML |
Test runner | TestNG |
Build tool | maven |
CI tool | jenkins |
Runtime environment | Docker-Zalenium |
Scenario writing | Markdown files |
Packaging | JAR |
Communication client Client Communication Management (CCM) includes all services and technologies that enable document composition, management and distribution (PDF, Html, paper…) for the companies that use it. Documents are the privileged intermediaries between companies and their clients. They are the first means of communication. Fekra Consulting provides Desktop Publishing solutions with the main CCM editors […]
Do not hesitate to contact us should you need any further information. Contact us