[BDDFramework] Site properties should be used for static data

[BDDFramework] Site properties should be used for static data

  
Forge Component
(9)
Published on 2017-07-03 by João Proença
9 votes
Published on 2017-07-03 by João Proença

Hello, 

we just started using the BDDFramework component and are experiencing some locking issues due to the frequently updates on the siteproperty entity (and deploying espaces at the same time). 

I would advise to write the siteproperties to an entity (e.g. ScenarioResults) to avoid locking a the SiteProperty entity (and avoid invalidation of espaces). 

We are currently working on it. 

Regards,

Hans

@Dans

But are you changing the Site Property during the deployment, is that it?

The BDD Framework is heavily making use of Site properties for status information during the run of a test scenario.

One of the Best practices is "Avoid changing Site Properties values in your logic"; because updating site properties invalidates the cache and requires the properties to be reloaded from the database.

When publishing a module and running a BDD Test for another module; the publish gives a error because of invalidation of the cache.


Matthias Preuter wrote:

The BDD Framework is heavily making use of Site properties for status information during the run of a test scenario.

Ouch! And this is an component from an OutSystems employee...


Hey everyone.

Thanks for the feedback. I'm already speaking with Matthias to incorporate what he has already developed in his own version of the framework, which doesn't rely on Site Properties.

Cheers!