This repository has been archived by the owner on Mar 12, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
Define a concept how to store types of never explored actions #34
Labels
enhancement
New feature or request
Comments
The action type is only part of Surili. Surili can get the types from the concrete actions. The state graph can store a counter of unexplored action types only. This counter has to be set once the state is created. Maybe we should distinguish between:
The counter should be decreased whenever an unexplored action is executed? |
tdauth
added a commit
that referenced
this issue
May 14, 2019
tdauth
added a commit
that referenced
this issue
May 14, 2019
- getState returns an Option - Remove convenient method executeAction based on SutStates - Store only a counter not a set of ActionIdentifiers - Adapt unit tests
rebazer
pushed a commit
that referenced
this issue
May 14, 2019
rebazer
pushed a commit
that referenced
this issue
May 14, 2019
- getState returns an Option - Remove convenient method executeAction based on SutStates - Store only a counter not a set of ActionIdentifiers - Adapt unit tests
tdauth
added a commit
that referenced
this issue
May 14, 2019
tdauth
added a commit
that referenced
this issue
May 14, 2019
- getState returns an Option - Remove convenient method executeAction based on SutStates - Store only a counter not a set of ActionIdentifiers - Adapt unit tests
tdauth
added a commit
that referenced
this issue
May 14, 2019
tdauth
added a commit
that referenced
this issue
May 21, 2019
tdauth
added a commit
that referenced
this issue
May 21, 2019
tdauth
added a commit
that referenced
this issue
May 21, 2019
rebazer
pushed a commit
that referenced
this issue
May 21, 2019
rebazer
pushed a commit
that referenced
this issue
May 21, 2019
- getState returns an Option - Remove convenient method executeAction based on SutStates - Store only a counter not a set of ActionIdentifiers - Adapt unit tests
rebazer
pushed a commit
that referenced
this issue
May 21, 2019
rebazer
pushed a commit
that referenced
this issue
May 21, 2019
rebazer
pushed a commit
that referenced
this issue
May 21, 2019
rebazer
pushed a commit
that referenced
this issue
May 21, 2019
rebazer
pushed a commit
that referenced
this issue
May 21, 2019
rebazer
pushed a commit
that referenced
this issue
May 21, 2019
rebazer
pushed a commit
that referenced
this issue
May 21, 2019
- getState returns an Option - Remove convenient method executeAction based on SutStates - Store only a counter not a set of ActionIdentifiers - Adapt unit tests
rebazer
pushed a commit
that referenced
this issue
May 21, 2019
rebazer
pushed a commit
that referenced
this issue
May 21, 2019
rebazer
pushed a commit
that referenced
this issue
May 21, 2019
rebazer
pushed a commit
that referenced
this issue
May 21, 2019
Added ActionType to the state graph. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
For more complex strategies like
ToStateWithUnexploredActions
in the legacy code, we need to know which actions have not been explored in all states.Note that we cannot really limit actions such as
ChangeValueOfAction
because we have to fill them with random values.Hence, it would make more sense to store types of never explored actions together with the XPath of the target element.
Note that these never explored action types must be passed when getting a state like in the legacy API.
The text was updated successfully, but these errors were encountered: