Feature Description
Details
A while back, we created a frequency-scenario-templates repo with a number of utility and helper methods cloned from our Frequency E2E test harness. The purpose of this repo was to provide helpers and convenience functions to facilitate JS-scripted blockchain setup scripts in various scenarios, mainly for use in seeding test scenarios and other development purposes.
Both frequency-scenario-templates and the E2E test harness have continued to grow; however, maintaining frequency-scenario-templates as a separate repo introduces a dependency maintenance issue; as we continue to release versions of Frequency and its JS libraries, it becomes cumbersome to then also have to update the other repo with the appropriate dependencies.
It would be advantageous to combine the E2E test harness functionality with the frequency-scenario-template capabilities, and maintain as an independently-published package within the Frequency repo, much as api-augment, ethereum-utils, and recovery-sdk are. In this way, the E2E tests could depend on this "internal" package, and other projects could depend on the published package, mostly without disruption.
Searched for Related Issues
Feature Description
Details
A while back, we created a
frequency-scenario-templatesrepo with a number of utility and helper methods cloned from our Frequency E2E test harness. The purpose of this repo was to provide helpers and convenience functions to facilitate JS-scripted blockchain setup scripts in various scenarios, mainly for use in seeding test scenarios and other development purposes.Both
frequency-scenario-templatesand the E2E test harness have continued to grow; however, maintainingfrequency-scenario-templatesas a separate repo introduces a dependency maintenance issue; as we continue to release versions of Frequency and its JS libraries, it becomes cumbersome to then also have to update the other repo with the appropriate dependencies.It would be advantageous to combine the E2E test harness functionality with the
frequency-scenario-templatecapabilities, and maintain as an independently-published package within the Frequency repo, much asapi-augment,ethereum-utils, andrecovery-sdkare. In this way, the E2E tests could depend on this "internal" package, and other projects could depend on the published package, mostly without disruption.Searched for Related Issues