You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using a base experiment class to manage our publish logic. All the actual experiments are extending from this base class. However, if we set raise_on_mismatches to this base class the result doesn't take effect as the method is using class instance variables(instead of class variables). In the end, people occasionally forget to use this test helper for their newly created experiments.
It would be great if we can manage this test helper via a base class. To elaborate more on this, this is somewhat our structure;
classBaseExperimentincludeScientist::Experimentdefinitialize# setting up some instance variables mainly needed for publish logicenddefpublish(result)# some custom logicendendclassWidgetExperiment < BaseExperimentdefinitialize# setting up custom variablessuperenddefenabled?# custom enabled logicendendclassAnotherExperiment < BaseExperiment# similar context with widget experimentend
What we want is to use BaseExperiment.raise_on_mismatches = true to ensure all child experiments are tested on tests without needed a separate test setup. Would such a need make sense to you?
The text was updated successfully, but these errors were encountered:
We are using a base experiment class to manage our publish logic. All the actual experiments are extending from this base class. However, if we set raise_on_mismatches to this base class the result doesn't take effect as the method is using class instance variables(instead of class variables). In the end, people occasionally forget to use this test helper for their newly created experiments.
It would be great if we can manage this test helper via a base class. To elaborate more on this, this is somewhat our structure;
classBaseExperimentincludeScientist::Experimentdefinitialize# setting up some instance variables mainly needed for publish logicenddefpublish(result)# some custom logicendendclassWidgetExperiment < BaseExperimentdefinitialize# setting up custom variablessuperenddefenabled?# custom enabled logicendendclassAnotherExperiment < BaseExperiment# similar context with widget experimentend
What we want is to use BaseExperiment.raise_on_mismatches = true to ensure all child experiments are tested on tests without needed a separate test setup. Would such a need make sense to you?
We are using a base experiment class to manage our publish logic. All the actual experiments are extending from this base class. However, if we set raise_on_mismatches to this base class the result doesn't take effect as the method is using class instance variables(instead of class variables). In the end, people occasionally forget to use this test helper for their newly created experiments.
It would be great if we can manage this test helper via a base class. To elaborate more on this, this is somewhat our structure;
What we want is to use
BaseExperiment.raise_on_mismatches = true
to ensure all child experiments are tested on tests without needed a separate test setup. Would such a need make sense to you?The text was updated successfully, but these errors were encountered: