assertj / assertj/assertj-swing

FEST aborts TestNG Test Execution

Abierto
#46 2 comentarios 0 reacciones 0 asignados Ver en GitHub
bug import from fest-swing Major
Lenguaje dominante
Java
Estrellas
121
Forks
52
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

_Issue by **[Alex Ruiz](http://jira.codehaus.org/secure/ViewProfile.jspa?name=alexruiz)** from Sun, 2 Aug 2009 23:56:23 -0500_
_Originally opened as http://jira.codehaus.org/browse/FEST-208_

---

"ScreenshotOnFailureListenerTest " class seems to be capable of taking screen shot only once in test failure for a method, when I combine this with data driven testing of TestNG, my test execution is aborted as FEST tries to save another image on same path, and I get exception like this -

*******************

Exception in thread "main" org.fest.util.FilesException: Unable to create the new file 'D:\Workspace\FunctionLibrary\reportng\SelTestAutomation Results\com.test.newtest.Login.login.png': a file was found with the same path

*******************

This happens cause "screenshotFileName" method would create same file name again and eventually fail in saving another image with same name in that location. May be we we could append UUID with it to make it unique for each instance of failure.

I could not find an url to browser source code locally and modify this method and build FEST for me, Could any one plase direct me to source core url?

Thanks in Advance,

Tarun K

---

votes (original issue): 1
watches (original issue): 0

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Comienza con ScreenshotOnFailureListenerTest y el método screenshotFileName mencionado en el informe, y luego reproduce el fallo mediante pruebas basadas en datos de TestNG. Verifica que los fallos repetidos produzcan rutas de captura de pantalla distintas y que la ejecución de las pruebas ya no se cancele.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
java
Área
testing
Tipo de issue
Error
Dificultad
3/5
Tiempo estimado
1-2 días
Estado de actividad
Estancado
Claridad
Bastante claro
Aptitud para principiantes
35/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.