As a user of scenarioo I want the scenarioo writer libraries at least to give me some comfort to make integration into most testing technologies a little bit easier.
Following things might be good if the libraries supports it:
config flag to turn off writing the files and taking screenshots (such that user of the library does not have to pollute its code with ifs everywhere)
Some annotations that can be reused for descriptions, Labels etc. on tests and test classes
some convenience to collect things like screen annotations and additional meta data more easily to be stored on next step, scenario, useCase etc. (--> context objects)
maybe even possibility to store something on last step (only write on next step, to give user possibility to still ammend some data after the screenshot have been taken (especially for ScenariooJS)
asynch write
some more guidance on how to use and integrate it in concrete (most used) testing tools might be helpful
we should decide what should go directly into which libraries, and what not, and maybe to create more libraries e.g. like "jselenioo", "selenioo#", ...
Example / Inspiration:
ScenariooJS is a good example to inspire us, on what we could improve in other libraries, On the other hand the current design of ScenariooJS also has some disadvantages (not so easy to control what data to write, or write additional data).
currently ScenariooJS comes with both a pure scenarioo writer that is WebdriverJS independent, and a WebdriverJS and jasmine dependent integration. In some parts it might be even dependent on protractor? (which shouldnt be the case)
similar approach might be interesting for Java and C#
As a user of scenarioo I want the scenarioo writer libraries at least to give me some comfort to make integration into most testing technologies a little bit easier.
Following things might be good if the libraries supports it:
Example / Inspiration: