allure-framework / allure-framework/allure2
Scroll to the top of the page in failed test
- Dominant language
- HTML
- Stars
- 5.5k
- Forks
- 782
- Avg merge
- 2d 33m
- Merged PRs (30d)
- 16
Description
[//]: # (
. Note: for support questions, please use Stackoverflow or Gitter**.
. This repository's issues are reserved for feature requests and bug reports.
.
. In case of any problems with Allure Jenkins plugin** please use the following repository
. to create an issue: https://github.com/jenkinsci/allure-plugin/issues
.
. Make sure you have a clear name for your issue. The name should start with a capital
. letter and no dot is required in the end of the sentence. An example of good issue names:
.
. - The report is broken in IE11
. - Add an ability to disable default plugins
. - Support emoji in test descriptions
)
#### I'm submitting a ...
- [x] bug report
- [ ] feature request
- [ ] support request => Please do not submit support request here, see note at the top of this template.
#### What is the current behavior?
When you open an attachment, the focus is shifted to the top of the page
#### If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal
I scroll the fallen test to the end of the page. I open sub-tests and open the attachment (screenshot) in the subtest, and then scrolls up the page
#### What is the expected behavior?
When you open the attachment, the focus remains in place
#### What is the motivation / use case for changing the behavior?
This is necessary for the convenience of viewing errors
#### Please tell us about your environment:
| Allure version | 2.4.1 |
|-----|----|
| Browser | Chrome 52 |
| Test framework | testng@6.11 |
[//]: # (
. e.g. detailed explanation, stacktraces, related issues, suggestions
. how to fix, links for us to have more context, eg. Stackoverflow, Gitter etc
)
Contributor guide
Research direction
No source files or tests are named. Reproduce the attachment-opening flow in Allure Report 2.4.1 with Chrome 52: scroll a failed test, open a sub-test attachment, and verify that the page remains at the prior scroll position.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100