Alexey Dmitriev, я уже писала, что нашим разработчикам до всего этого нет никакого дела, они сами пытаются у меня научиться авто-тестированию. Я пробовала к ним обращаться - все бестолку , поэтому пишу сюда.
Dmitry Roo, спасибо огромное! Открыла отчет успешно. Как мне Вас отблагодарить ? Вы меня так выручили. Могу картинку нарисовать, связать зверушку любимую, песню спеть (увлекаюсь творчеством) :)
Dmitry Roo, Спасибо за ответ! Нашла ошибку в самом проекте, тест успешный, запустился, по сути все отработал верно.
Есть еще вопрос : по запуску команды mvn allure:serve
Возникает вот такая ошибка : с чем может быть связано ?
Could not open the report in browser, try to open it manually 172.27.125.235:50892: {}
java.io.IOException: Failed to open 172.27.125.235:50892. Error message: Указанному файлу не сопоставлено ни одно приложение для выполнения данной операции.
at java.desktop/sun.awt.windows.WDesktopPeer.ShellExecute(WDesktopPeer.java:115)
at java.desktop/sun.awt.windows.WDesktopPeer.browse(WDesktopPeer.java:101)
at java.desktop/java.awt.Desktop.browse(Desktop.java:533)
at io.qameta.allure.Commands.openBrowser(Commands.java:228)
at io.qameta.allure.Commands.open(Commands.java:153)
at io.qameta.allure.Commands.serve(Commands.java:137)
at io.qameta.allure.CommandLine.run(CommandLine.java:159)
at java.base/java.util.Optional.orElseGet(Optional.java:364)
at io.qameta.allure.CommandLine.main(CommandLine.java:88)
Server started at . Press to exit
Dmitry Roo, пишет, что собирается, сами тесты запускаются, но по сути не происходит самого действия в приложении - должна создаться конкретная запись по тесту, я ее в приложении не вижу, вижу только, как тесты успешно проходят.
на данном этапе вот такая ошибка : [WARNING]
[WARNING] Some problems were encountered while building the effective model for selenide-boilerplate:selenide-boilerplate:jar:1.0-SNAPSHOT
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: org.testng:testng:jar -> version 6.14.3 vs 7.8.0 @ line 48, column 21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]
[INFO]
[INFO] -------------< selenide-boilerplate:selenide-boilerplate >--------------
[INFO] Building selenide-boilerplate 1.0-SNAPSHOT
[INFO] from pom.xml
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- allure:2.14.0:serve (default-cli) @ selenide-boilerplate ---
[INFO] Rendering content with org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
[INFO] Allure installation directory C:\ShakhIn\QA_AUTOMATE\Projects\DEV/.allure
[INFO] Try to finding out allure 2.14.0
[INFO] Generate Allure report (serve) with version 2.14.0
[INFO] Generate Allure report to C:\ShakhIn\QA_AUTOMATE\Projects\DEV\target\site/allure-maven-plugin
[INFO] Found results directory C:\ShakhIn\QA_AUTOMATE\Projects\DEV\target\allure-results
[INFO] Can't find information about categories
[INFO] Generate report to C:\ShakhIn\QA_AUTOMATE\Projects\DEV\target\site\allure-maven-plugin
Generating report to temp directory...
Report successfully generated to C:\Users\user\AppData\Local\Temp\6929213201576252122\allure-report
Starting web server...
2024-10-01 11:12:23.665:INFO::main: Logging initialized @3185ms to org.eclipse.jetty.util.log.StdErrLog
Could not open the report in browser, try to open it manually 172.27.123.108:58582: {}
java.io.IOException: Failed to open 172.27.123.108:58582. Error message: Указанному файлу не сопоставлено ни одно приложение для выполнения данной операции.
at java.desktop/sun.awt.windows.WDesktopPeer.ShellExecute(WDesktopPeer.java:115)
at java.desktop/sun.awt.windows.WDesktopPeer.browse(WDesktopPeer.java:101)
at java.desktop/java.awt.Desktop.browse(Desktop.java:533)
at io.qameta.allure.Commands.openBrowser(Commands.java:222)
at io.qameta.allure.Commands.open(Commands.java:152)
at io.qameta.allure.Commands.serve(Commands.java:136)
at io.qameta.allure.CommandLine.run(CommandLine.java:159)
at java.base/java.util.Optional.orElseGet(Optional.java:364)
at io.qameta.allure.CommandLine.main(CommandLine.java:88)
Server started at . Press to exit
ошибка
[INFO]
[INFO] --- resources:3.3.1:resources (default-resources) @ selenide-boilerplate ---
[INFO] Copying 1 resource from src\main\resources to target\classes
[INFO]
[INFO] --- compiler:3.11.0:compile (default-compile) @ selenide-boilerplate ---
[INFO] Changes detected - recompiling the module! :dependency
[INFO] Compiling 83 source files with javac [debug target 1.9] to target\classes
[WARNING] system modules path not set in conjunction with -source 9
[INFO]
[INFO] --- resources:3.3.1:testResources (default-testResources) @ selenide-boilerplate ---
[INFO] Copying 2 resources from src\test\resources to target\test-classes
[INFO]
[INFO] --- compiler:3.11.0:testCompile (default-testCompile) @ selenide-boilerplate ---
[INFO] Changes detected - recompiling the module! :dependency
[INFO] Compiling 3 source files with javac [debug target 1.9] to target\test-classes
[INFO] -------------------------------------------------------------
[WARNING] COMPILATION WARNING :
[INFO] -------------------------------------------------------------
[WARNING] system modules path not set in conjunction with -source 9
[INFO] 1 warning
[INFO] -------------------------------------------------------------
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /C:/ShakhIn/QA_AUTOMATE/Projects/DEV/src/test/java/A_BaseTestListener.java:[4,24] package io.qameta.allure does not exist
[ERROR] /C:/ShakhIn/QA_AUTOMATE/Projects/DEV/src/test/java/A_BaseTestListener.java:[5,33] package io.qameta.allure.listener does not exist
[ERROR] /C:/ShakhIn/QA_AUTOMATE/Projects/DEV/src/test/java/A_BaseTest.java:[4,24] package io.qameta.allure does not exist
[ERROR] /C:/ShakhIn/QA_AUTOMATE/Projects/DEV/src/test/java/A_BaseTest.java:[14,24] package io.qameta.allure does not exist
[INFO] 4 errors
[INFO] -------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 17.821 s
[INFO] Finished at: 2024-10-01T10:47:00+03:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.11.0:testCompile (default-testCompile) on project selenide-boilerplate: Compilation failure: Compilation failure:
[ERROR] /C:/ShakhIn/QA_AUTOMATE/Projects/DEV/src/test/java/A_BaseTestListener.java:[4,24] package io.qameta.allure does not exist
[ERROR] /C:/ShakhIn/QA_AUTOMATE/Projects/DEV/src/test/java/A_BaseTestListener.java:[5,33] package io.qameta.allure.listener does not exist
[ERROR] /C:/ShakhIn/QA_AUTOMATE/Projects/DEV/src/test/java/A_BaseTest.java:[4,24] package io.qameta.allure does not exist
[ERROR] /C:/ShakhIn/QA_AUTOMATE/Projects/DEV/src/test/java/A_BaseTest.java:[14,24] package io.qameta.allure does not exist
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.11.0:testCompile (default-testCompile) on project selenide-boilerplate: Compilation failure
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:333)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:316)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:212)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:174)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 (MojoExecutor.java:75)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run (MojoExecutor.java:162)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute (DefaultMojosExecutionStrategy.java:39)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:159)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:105)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:73)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:53)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:118)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
at jdk.internal.reflect.DirectMethodHandleAccessor.invoke (DirectMethodHandleAccessor.java:104)
at java.lang.reflect.Method.invoke (Method.java:578)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:283)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:226)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:407)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:348)
Caused by: org.apache.maven.plugin.compiler.CompilationFailureException: Compilation failure
at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute (AbstractCompilerMojo.java:1212)
at org.apache.maven.plugin.compiler.TestCompilerMojo.execute (TestCompilerMojo.java:199)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:126)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:328)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:316)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:212)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:174)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 (MojoExecutor.java:75)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run (MojoExecutor.java:162)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute (DefaultMojosExecutionStrategy.java:39)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:159)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:105)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:73)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:53)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:118)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
at jdk.internal.reflect.DirectMethodHandleAccessor.invoke (DirectMethodHandleAccessor.java:104)
at java.lang.reflect.Method.invoke (Method.java:578)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:283)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:226)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:407)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:348)
[ERROR]
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] cwiki.apache.org/confluence/display/MAVEN/MojoFail...
PS C:\ShakhIn\QA_AUTOMATE\Projects\DEV>
на команду с терминала: mvn package
[WARNING]
[WARNING] Some problems were encountered while building the effective model for selenide-boilerplate:selenide-boilerplate:jar:1.0-SNAPSHOT
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: org.testng:testng:jar -> version 6.14.3 vs 7.8.0 @ line 46, column 21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]
[INFO]
[INFO] -------------< selenide-boilerplate:selenide-boilerplate >--------------
[INFO] Building selenide-boilerplate 1.0-SNAPSHOT
[INFO] from pom.xml
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- allure:2.12.0:serve (default-cli) @ selenide-boilerplate ---
[INFO] Allure installation directory C:\ShakhIn\QA_AUTOMATE\Projects\Common_Dic/.allure
[INFO] Try to finding out allure 2.14.0
[INFO] Generate Allure report (serve) with version 2.14.0
[INFO] Generate Allure report to C:\ShakhIn\QA_AUTOMATE\Projects\Common_Dic\target\site/allure-maven-plugin
[INFO] Found results directory C:\ShakhIn\QA_AUTOMATE\Projects\Common_Dic\target\allure-results
[INFO] Can't find information about categories
[INFO] Generate report to C:\ShakhIn\QA_AUTOMATE\Projects\Common_Dic\target\site\allure-maven-plugin
Generating report to temp directory...
Report successfully generated to C:\Users\user\AppData\Local\Temp\15223321470327273058\allure-report
Starting web server...
2024-09-30 16:52:12.158:INFO::main: Logging initialized @3101ms to org.eclipse.jetty.util.log.StdErrLog
Could not open the report in browser, try to open it manually 172.27.123.129:50091: {}
java.io.IOException: Failed to open 172.27.123.129:50091. Error message: Указанному файлу не сопоставлено ни одно приложение для выполнения данной операции.
at java.desktop/sun.awt.windows.WDesktopPeer.ShellExecute(WDesktopPeer.java:115)
at java.desktop/sun.awt.windows.WDesktopPeer.browse(WDesktopPeer.java:101)
at java.desktop/java.awt.Desktop.browse(Desktop.java:533)
at io.qameta.allure.Commands.openBrowser(Commands.java:222)
at io.qameta.allure.Commands.open(Commands.java:152)
at io.qameta.allure.Commands.serve(Commands.java:136)
at io.qameta.allure.CommandLine.run(CommandLine.java:159)
at java.base/java.util.Optional.orElseGet(Optional.java:364)
at io.qameta.allure.CommandLine.main(CommandLine.java:88)
Server started at . Press to exit
@Dmitry Roo Dmitry Roo Дмитрий, поняла, спасибо, попробую. У меня еще подозрение, что на тестируемом сайте логаут не работает. Раньше была проблема с ним.
Dmitry Roo Dmitry Roo
Добавила перед тестом:
public SelenideElement TestLogOut_1 = $(By.name("User – Circle White"));
public SelenideElement TestLogOut_2 = $(By.id("log-out"));
@BeforeTest
public void clearCookies() {
helpers.Driver.clearCookies();
}
// public void tearDown() {
// Driver.close();
// }
public void testLogout() {
TestLogOut_1.click();
TestLogOut_2.click();
Dmitry Roo Dmitry Roo Получается, что он в первом тесте авторизуется, переходит на страницу, выполняя все необходимые действия. Во втором тесте авторизуется, переходит на другую страницу и останавливается. При запуске тестов в первом я вижу, как эти действия выполняются, во втором авторизация как будто бы пропущена и сразу вижу вторую страницу.
