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

Define a concept how to store types of never explored actions #34

Closed
tdauth opened this issue Apr 23, 2019 · 2 comments
Closed

Define a concept how to store types of never explored actions #34

tdauth opened this issue Apr 23, 2019 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@tdauth
Copy link
Contributor

tdauth commented Apr 23, 2019

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.

@tdauth tdauth added the enhancement New feature or request label Apr 23, 2019
@tdauth tdauth self-assigned this Apr 23, 2019
@tdauth
Copy link
Contributor Author

tdauth commented May 14, 2019

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:

createState(sutState : SutState, neverExploredActionTypesCounter : Int) : State
getState(sutState : SutState) : Option[State]

The counter should be decreased whenever an unexplored action is executed?

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 14, 2019
tdauth added 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
rebazer pushed a commit that referenced this issue May 14, 2019
rebazer pushed a commit that referenced this issue May 14, 2019
rebazer pushed 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 14, 2019
tdauth added a commit that referenced this issue May 14, 2019
tdauth added a commit that referenced this issue May 14, 2019
tdauth added a commit that referenced this issue May 15, 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
- 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
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
rebazer pushed a commit that referenced this issue May 21, 2019
@tdauth
Copy link
Contributor Author

tdauth commented Jun 11, 2019

Added ActionType to the state graph.

@tdauth tdauth closed this as completed Jun 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Development

No branches or pull requests

1 participant