Skip to content
This repository has been archived by the owner on Mar 12, 2020. It is now read-only.

Use retest-model and the Selenium API to identify states and actions #3

Closed
tdauth opened this issue Oct 23, 2018 · 1 comment
Closed

Use retest-model and the Selenium API to identify states and actions #3

tdauth opened this issue Oct 23, 2018 · 1 comment
Assignees
@tdauth
Labels
enhancement New feature or request

Comments

@tdauth
Copy link
Contributor

tdauth commented Oct 23, 2018 •
edited
Loading

The package de.retest.guistatemachine.model contains model definitions based on the thesis by Furrer.
Currently, the REST service uses custom case classes.
Clarify, how the actual model looks like/should look like and adapt traits/classes in the model package.
Remove the case classes for the REST service afterwards.

The Furrer model is invalid. Specify the model by debugging the application.

RootElements from https://mvnrepository.com/artifact/de.retest/retest-model identify a state.
A Selenium API Action identifies an action/transition.
@tdauth tdauth added the enhancement New feature or request label Oct 23, 2018
@tdauth tdauth self-assigned this Oct 23, 2018
@tdauth tdauth changed the title Clarify and adapt model Use retest-model and the Selenium API to identify states and actions Oct 31, 2018
tdauth added a commit that referenced this issue Nov 5, 2018
@tdauth
Add API package and refactor code #3 #4
d729a51 
- Move REST part into package rest
- Add api package and retest/Selenium dependencies
- Use scalamock for mocking
- Add scalafmt sbt plugin and rules file
- Refactor DSL code
@tdauth
Copy link
Contributor Author

tdauth commented Nov 5, 2018

Done in the package api.

@tdauth tdauth closed this as completed Nov 5, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@tdauth tdauth

Labels
enhancement New feature or request
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tdauth