-
Notifications
You must be signed in to change notification settings - Fork 3
Home
Dorian Cransac edited this page Jul 15, 2019
·
9 revisions
Documentation available at : https://step.exense.ch/knowledgebase
Official Website : http://step.exense.ch
- Coming soon
Evaluation done as of March 31st (a bit late, sorry)
Goal | Completion % | Comment/Reason | EE only |
---|---|---|---|
** Devops ** | |||
Common test plan format | 80 | Step Natural Language + PlanBuilder released. Only missing code or at least unit test generation for local debugging | |
New classes for client-side triggers | 100 | "STEPClient" released | X |
** Mobile ** | |||
Ability to test Android apps & browser | 100 | Accomplished Java agent + Appium, also offered as a Cloud service | |
Appium integration | 100 | Tested and now officially supported. No need for a dedicated plugin though. | |
** HTTP ** | |||
HAR Replay | 30 | Achieved at a client, not officially integrated or supported yet. Official HTTP keywords offered as an alternative | |
Custom script generation | 0 | Abandoned for now. If anything happens in this department, it'll be through the HAR replay(er). | |
OOTB support of SSL contexts | 90 | Provided via our official HTTP keyword package. Just not officially released/OS'ed yet, but in use at clients. | |
Gatling & co | 0 | Not a high priority at this point. | |
** Keyword dev ** | |||
Helper classes | 60 | In use internally and at some clients, not officially released yet. | |
API Refactoring | 70 | Major improvements have been done. Inputs & Outputs still expected to change. API has now be desync'd from STEP for easier maintenance | |
Starter kits | 100 | Sample projects implemented | |
Javadocs | 100 | ||
** Plans dev ** | |||
Generic keywords | 80 | Mecanism implemented. Done in EE for broker, in progress for HTTP | X |
Plan templates | 100 | Available for import under Libraries in our docs | |
Refactoring of artefacts & new artefacts | 100 | ||
Previous KW output reference | 100 | ||
Init hooks | 0 | Can be handled in other ways, low prio | |
** Ops ** | |||
Export/Import | 100 | Done for Plans | |
Data retention strategy | 100 | Done but can be improved | |
Admin view improvements | 0 | Could not do in time. | |
Self-Monitoring | 50 | Not published yet but new features in use as beta version at key clients. | |
** Misc ** | |||
Doc refactoring & migration | 60 | Should be released by May | |
Github status & widget | 0 | Low prio. | |
Artefact publication in Maven | 0 | Low prio. | |
** Not in roadmap but done anyways ** | |||
Resource manager | |||
Notifications | |||
Pupeteer | |||
Async support | |||
& much more (see release notes)... |
- Introduction of a common format for test plans (with translation between Java code and persisted plans in the web app) to enable wider cross-practice collaboration
- Introduction of new client classes providing client-side triggers, remote test plan execution and remote keyword execution to provide developers with more flexibility, facilitate integration with build processes and allow developers to commit test plans as part of their projects
- Support of both native mobile applications and mobile-based browsers (as a simulation and on real devices)
- Integration with popular mobile testing frameworks, preferably based on the WebDriver API such as Appium (Selendroid a possibility)
- Support of HAR replays
- Custom script generation
- Out of the box support of SSL contexts
- Possible integration with additional HTTP frameworks such as Gatling (to complete the existing library: JMeter, Grinder and SoapUI)
- Exposure of frequently used Helper classes for keyword input / output management and error handling
- API refactoring (including the replacement the javax json library)
- Publication of starter kits and examples of best practices for the most common types of projects
- Publication of detailed Javadocs and source jars
- Introduction of generic keywords for the most common technical use cases and out-of-the-box support of standard protocols (htttp/s, ftp/s, etc) without having to use any plugins (grinder, jmeter, etc)
- Introduction of test plan templates for the most common use cases (data-driven, load and monitoring scenarios)
- Refactoring of key artefacts such as "Set", "Composite" KWs or "CallFunction" and introduction of new artefacts in order to enhance test plan modularity and reusability
- Automatic access to previous keyword outputs for finer linkage
- Addition of various Init/Pre and Exit/Post hooks, destined to be used primarily in parallel artefacts (For, ForEach, ThreadGroup), as a first step toward the support of a jointpoint-style Test plan API
- Introduction of one-click import and export for most objects (in particular Test plans and Executions)
- Introduction of data retention strategies
- Enhancements in the admin view to publish all of the internal technical information (controller + agents)
- Self-monitoring (at system, middleware and client code levels)
- Migration, refactoring and update of the documentation
- Improved project status on github (nightly buildwidget)
- Direct artefact publication to the Maven Central repo