@Paulina Buzderewicz: new steps are added but they are not included when running the test for some reason (it only starts working after a few attempts to run)
@Mateusz Kwiatkowski: we cannot run a single functional test
@Nikodem Graczewski (Unlicensed): the tests may be failing if we forget to take into consideration that the steps take some time and we may need to wait for the loading modal to disappear
@Mateusz Kwiatkowski: they run on the test server so the results depend on what other changes have been made there
@Łukasz Lewczyński (Deactivated): everything with the functional tests take long: the framework is big so it takes quite some time to download, starting the tests and running them also takes quite some time
@Łukasz Lewczyński (Deactivated): the results of the tests are printed only after they all run, and not as they are executed
@Mateusz Kwiatkowski: there are some “random” problems and we don’t always know where they are coming from
@Nikodem Graczewski (Unlicensed): restrictions with view port - some elements may not be visible for the web driver, even though they are present on the page
@Łukasz Lewczyński (Deactivated): not much experience with the framework and e2e tests
@Mateusz Kwiatkowski: we don’t have any guides/docs on writing functional tests in OpenLMIS
@Nikodem Graczewski (Unlicensed): there’s a mess with some given/when/then steps - unnecessary redundancy and different implementations of very similar things
@Mateusz Kwiatkowski: no easy way to debug a concrete step