Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for recording state in output data #114

Closed
annika-FTB opened this issue Oct 9, 2017 · 2 comments
Closed

Support for recording state in output data #114

annika-FTB opened this issue Oct 9, 2017 · 2 comments
Assignees
Labels

Comments

@annika-FTB
Copy link

In DOM Tree testing scripts are applied so that the test subject can be in "a specific state (be it the initial state or any other)" (Section 4.1).

This could affect the position of an element in the DOM. Please elaborate how is this recorded in the output data. Two options come to mind:

(1) A pointer can be used to indicate where the selected item exists within the web page or other test subject. The pointer method used in the output data of an ACT Rule must include the pointer method used in Implementation Test Cases.

OR (2) As part of the test subject

@nitedog
Copy link
Contributor

nitedog commented Jan 4, 2018

This is not directly part of the ACT Rules Format, but the related output format based on EARL that we are looking at developing to support the test cases (likely a JSON serialization of EARL).

In EARL, the specific state is recorded as part of the test subject. For example, stating the DOM Tree as the test subject, or by including the HTTP exchanges to define the specific state of the web content. The pointers then refer to the position, item, or other identification within the test subject.

That is, the model of EARL maps to point (1) in your question above. Both the type of test subject and pointer method should be described in the output data.

@nitedog nitedog closed this as completed Jan 29, 2018
@nitedog
Copy link
Contributor

nitedog commented Jan 29, 2018

@annika-FTB please see the response above and feel free to re-open, as needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants