assertj / assertj/assertj-swing
Make ScreenshotOnFailureResultFormatter take screenshots before the "After" methods are executed
- Langage dominant
- Java
- Étoiles
- 121
- Forks
- 52
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
_Issue by **[Brett Vasconcellos](http://jira.codehaus.org/secure/ViewProfile.jspa?name=brettv)** from Sat, 5 Jun 2010 14:18:21 -0500_
_Originally opened as http://jira.codehaus.org/browse/FEST-361_
---
In our project, we typically start the GUI under test in our Before methods and shut it down in the After methods.
We have a continuous integration setup with ant running the Fest tests on every check-in and would like to have screenshots of the failures, however it appears Junit 4.7 doesn't run the ScreenshotOnFailureResultFormatter code until after it's run the various teardown/After methods so we end up getting a screenshot of an empty desktop, similar to what was reported in FEST-216.
I am wondering whether it would be possible to somehow take and store the screenshot before the After methods run, in combination with the custom formatter to write them into the XML and thus include links to screenshots in the final HTML-based reports.
I'm no Junit expert, but I had a poke around in the source and it appears that perhaps extending org.junit.rules.TestWatchman instead of a custom runner might be the way to go – the failed method gets calls before the After methods do.
Now that I found this, a Google search shows me you may already be aware of the issue and TestWatchman approach.
---
votes (original issue): 0
watches (original issue): 0
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Commencez par suivre ScreenshotOnFailureResultFormatter et la manière dont il s’intègre au teardown de JUnit 4.7, puis comparez ce cycle de vie avec l’approche org.junit.rules.TestWatchman mentionnée. Le travail est terminé lorsque les échecs capturent la GUI avant que les méthodes After ne l’arrêtent et que les liens vers les captures d’écran restent disponibles dans les rapports XML et HTML.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- java
- Domaine
- desktop, testing
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 25/100