Article

Framework for automated testing of the Creatio platform.

Hi! Today I released a framework for automated testing of the Creatio platform.

The idea behind it is a simple language that a developer and a business analyst can both read. Because when you test Creatio, a large share of the work is the same kind of checking over and over: is the field on the page, is it filled in, is it required or read-only, do the configured rules behave the way they were set up.
So instead of page objects and selectors, a test looks like the picture below: a check that a field exists on the page, and that it takes a value.
You are probably looking at that GUID and the field code and thinking someone had to dig those out by hand. They did not. The framework opens the page itself, walks through its tabs, and writes down every field, button and tab it finds, with its caption and its type. You point it at a page and it describes itself. What you then write and edit are the checks.
Tests live in files with an .act extension. The framework picks up every test in the folder and runs them one by one, so a suite grows by adding a file, not by wiring anything up.
The part I am most pleased with is that a broken test costs you three seconds, not three minutes. Before a browser opens, the whole file is checked: unknown command, a field that is not on that page, an operator that makes no sense for a text field. You get every mistake at once, with line numbers, and you do not even need a running Creatio to find them. That makes it usable as a pre-commit check.
Which gives two things at once. A business analyst can read a test and change what it asserts without touching C#. And the same tests drop into a CI/CD pipeline, because the runner is a command-line tool that returns exit codes and writes reports.
Today it covers every field type on a Freedom UI page, plus buttons, tabs and the stage progress bar. It has been run against a live Creatio 8.3 instance, not only against mocks.
Next on the list:
- Grid detail support, so detail lists become testable
- Creating records automatically from a condition
- Richer reporting
- Making CI/CD integration simpler still
Open source under the MIT licence, built on .NET 8 and Playwright. Link in the comments.
If you work with Creatio and there is something you would want to test that this cannot reach yet, tell me. That is the most useful thing I can hear right now.

github:
https://github.com/artemivzhenko/automatic-creatio-tests

#Creatio #TestAutomation #FreedomUI #OpenSource #dotnet #QA #Playwright

Like 5

Like

Share

1 comments

Hi Artem, thanks for your product. Could you please clarify, I've tried to build your solution locally from local git repository, but got some errors: if I specify "dotnet build" only, then the systems writes "error MSB1003: Specify a project or solution file. The current working directory does not contain a project or solution file", if I add exact solution name CreatioAutoTests.slnx, it returns the error "CreatioAutoTests.slnx(1,
1): error MSB4068: The element <Solution> is unrecognized, or not supported in this context." What should I adjust? .NET SDK 8.0 is installed

Show all comments