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

Testcase history tab showing same date time for different runs #797

Closed
1 of 3 tasks
SohanTirpude opened this issue Mar 5, 2024 · 1 comment
Closed
1 of 3 tasks

Comments

@SohanTirpude
Copy link

SohanTirpude commented Mar 5, 2024

I'm submitting a ...

  • 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?

I am seeing same date time for same test case but different runs.

Screenshot 2024-03-05 at 5 25 49 PM

I am running this job in every 5 minute interval from Jenkins and some times I am seeing this abnormalities. BTW this is the demo test file I am using: https://github.com/fescobar/allure-docker-service-examples/blob/master/allure-docker-python-pytest-example/tests/demo_test.py

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

  1. Click on "Suite" tab.
  2. Click on test case
  3. Click on particular test
  4. Click on "History" tab
  5. For different runs, the date time is showing exact same.

What is the expected behavior?

For different test case runs, there should be different date time.

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

  • Allure version: 2.21.0
  • Test framework: pytest@8.0.1
  • Allure adaptor: allure-pytest@2.13.2

Other information

@baev
Copy link
Member

baev commented Mar 12, 2024

@baev baev closed this as not planned Won't fix, can't repro, duplicate, stale Mar 12, 2024
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