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

Dialog Disappears on Device Rotation #17

Open
reverse-unina opened this issue Jun 20, 2016 · 3 comments
Open

Dialog Disappears on Device Rotation #17

reverse-unina opened this issue Jun 20, 2016 · 3 comments

Comments

@reverse-unina
Copy link

When I perform these sequences of events, the dialog on screen disappears:

Sequence 1:

  1. click on ...(More Options)
  2. click on import
    [IF db in sd memory]
  3. Orientation Change

Sequence 2:

  1. Click on project
  2. Click on Edit Project
  3. Click on delete icon of a count element
  4. Orientation Change

Sequence 3: If there is at least a project saved with a link

  1. Click on project
  2. Click on Edit Project
  3. Click on delete icon of a link element
  4. Orientation Change

Sequence 4: If there is at least a project saved with an alert

  1. Click on a Project
  2. Click on Edit Icon of a Activity item
  3. Click on Delete Icon of an alert item
  4. Orientation Change

Sequence 5:

  1. Click on a project
  2. Click on ...(More Options...)
  3. Click on Duplicate Project
  4. Orientation Change

Sequence 6: if there is at least a project saved with an alert

  1. Click on a project
  2. Trigger Alert
  3. Orientation Change
@knirirr
Copy link
Owner

knirirr commented Jun 21, 2016

I'm not particularly bothered by most of these; 1-5 ask for confirmation of an action to modify data and if the dialog is dismissed then the modification does not take place, and so there's not a problem.

No. 6 is arguably worth dealing with although I don't think that it's a particularly high priority right now.

Of course, should you fancy taking a break from trying out your search-based Android testing then you're welcome to submit a pull request with the fix (as with #18).

@reverse-unina
Copy link
Author

Ok. I would greatly appreciate if you could let me know whether or not you consider them as failures. I am really interested in your point of view in my heuristic-based Android testing approach.

Regards

@knirirr
Copy link
Owner

knirirr commented Jun 21, 2016

All of these could be considered failures. However, I don't think that they could be considered serious because they are not likely to be encountered (my usage patterns never trigger them) and don't result in any data loss.

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

No branches or pull requests

2 participants