Hi Samvid,

Are you using the Framework for Manage?

https://epwt-www.mybluemix.net/software/support/trial/cst/programwebsite.wss?siteId=1790&h=null&p=null#

Hi @Samvid Shivram

The automation framework supports MAS 8.10/Manage 8.6 and you're trying to use it against MAS 8.11/Manage 8.7, which it does not support. It's failing when trying to log in because the login screen changed between releases. If you want to use MAS 8.11, you would have to update the code in the framework to support the login screen.

Thank you.

Hi @Kristin Fernandes

Thanks for the clarification.
Reading through the logs, I was able to find some of the class files and have updated the id/xpath of the elements (mainly username field, password field and continue button) as per the new login page for MAS 8.11. I have attached the modified files. Could you have a look and advise if there are more files to be updated?

Thank you.

Hi @Samvid Shivram

The automation framework supports MAS 8.10/Manage 8.6 and you're trying to use it against MAS 8.11/Manage 8.7, which it does not support. It's failing when trying to log in because the login screen changed between releases. If you want to use MAS 8.11, you would have to update the code in the framework to support the login screen.

Thank you.

Hi @Samvid Shivram

The MASPageLogin page should be the only file that needs to be updated in order to log into MAS 8.11. The IDs look correct to me so hopefully you've had a successful login after making the changes.

Thanks!

Hi @Kristin Fernandes

Thanks for the clarification.
Reading through the logs, I was able to find some of the class files and have updated the id/xpath of the elements (mainly username field, password field and continue button) as per the new login page for MAS 8.11. I have attached the modified files. Could you have a look and advise if there are more files to be updated?

Thank you.

Hi @Samvid Shivram

The automation framework supports MAS 8.10/Manage 8.6 and you're trying to use it against MAS 8.11/Manage 8.7, which it does not support. It's failing when trying to log in because the login screen changed between releases. If you want to use MAS 8.11, you would have to update the code in the framework to support the login screen.

Thank you.

Hi @Kristin Fernandes

The framework is still unable to find specific web elements on the MAS login page. I have attached the logs along with the properties file and .bin file.
Could you please have a look and advise? Thank you.

Hi @Samvid Shivram

The MASPageLogin page should be the only file that needs to be updated in order to log into MAS 8.11. The IDs look correct to me so hopefully you've had a successful login after making the changes.

Thanks!

Hi @Kristin Fernandes

Thanks for the clarification.
Reading through the logs, I was able to find some of the class files and have updated the id/xpath of the elements (mainly username field, password field and continue button) as per the new login page for MAS 8.11. I have attached the modified files. Could you have a look and advise if there are more files to be updated?

Thank you.

Hi @Samvid Shivram

The automation framework supports MAS 8.10/Manage 8.6 and you're trying to use it against MAS 8.11/Manage 8.7, which it does not support. It's failing when trying to log in because the login screen changed between releases. If you want to use MAS 8.11, you would have to update the code in the framework to support the login screen.

Thank you.

Hi @Samvid Shivram

Please remember that you are trying to use the framework on an unsupported version of MAS. We offer support via our community for the supported version only. The community can be found here: https://community.ibm.com/community/user/asset-facilities/viewdocument/ibm-maximo-test-automation-framewor

But since I can quickly answer your question I'll provide help with this one. If you go to Automation/framework/Page.java, you need to update line 25 to correctly reflect the login page.

Thanks.

Hi @Kristin Fernandes

The framework is still unable to find specific web elements on the MAS login page. I have attached the logs along with the properties file and .bin file.
Could you please have a look and advise? Thank you.

Hi @Samvid Shivram

The MASPageLogin page should be the only file that needs to be updated in order to log into MAS 8.11. The IDs look correct to me so hopefully you've had a successful login after making the changes.

Thanks!

Hi @Kristin Fernandes

Thanks for the clarification.
Reading through the logs, I was able to find some of the class files and have updated the id/xpath of the elements (mainly username field, password field and continue button) as per the new login page for MAS 8.11. I have attached the modified files. Could you have a look and advise if there are more files to be updated?

Thank you.

Hi @Samvid Shivram

The automation framework supports MAS 8.10/Manage 8.6 and you're trying to use it against MAS 8.11/Manage 8.7, which it does not support. It's failing when trying to log in because the login screen changed between releases. If you want to use MAS 8.11, you would have to update the code in the framework to support the login screen.

Thank you.

Hi @Kristin Fernandes

Many thanks! After updating the line 25 in Page.java with a relevant web element and couple of other file changes, I was able to successfully execute a test case. Do we have a time lead for Test Automation Support for MAS 8.11? Looking forward to your reply. 

Hi @Samvid Shivram

Please remember that you are trying to use the framework on an unsupported version of MAS. We offer support via our community for the supported version only. The community can be found here: https://community.ibm.com/community/user/asset-facilities/viewdocument/ibm-maximo-test-automation-framewor

But since I can quickly answer your question I'll provide help with this one. If you go to Automation/framework/Page.java, you need to update line 25 to correctly reflect the login page.

Thanks.

Hi @Kristin Fernandes

The framework is still unable to find specific web elements on the MAS login page. I have attached the logs along with the properties file and .bin file.
Could you please have a look and advise? Thank you.

Hi @Samvid Shivram

The MASPageLogin page should be the only file that needs to be updated in order to log into MAS 8.11. The IDs look correct to me so hopefully you've had a successful login after making the changes.

Thanks!

Hi @Kristin Fernandes

Thanks for the clarification.
Reading through the logs, I was able to find some of the class files and have updated the id/xpath of the elements (mainly username field, password field and continue button) as per the new login page for MAS 8.11. I have attached the modified files. Could you have a look and advise if there are more files to be updated?

Thank you.

Hi @Samvid Shivram

The automation framework supports MAS 8.10/Manage 8.6 and you're trying to use it against MAS 8.11/Manage 8.7, which it does not support. It's failing when trying to log in because the login screen changed between releases. If you want to use MAS 8.11, you would have to update the code in the framework to support the login screen.

Thank you.

Hi @Samvid Shivram

Happy to hear it's working! 

There is no release planned for MAS 8.11; the next release will be for MAS 9.0.

Thanks.

Hi @Kristin Fernandes

Many thanks! After updating the line 25 in Page.java with a relevant web element and couple of other file changes, I was able to successfully execute a test case. Do we have a time lead for Test Automation Support for MAS 8.11? Looking forward to your reply. 

Hi @Samvid Shivram

Please remember that you are trying to use the framework on an unsupported version of MAS. We offer support via our community for the supported version only. The community can be found here: https://community.ibm.com/community/user/asset-facilities/viewdocument/ibm-maximo-test-automation-framewor

But since I can quickly answer your question I'll provide help with this one. If you go to Automation/framework/Page.java, you need to update line 25 to correctly reflect the login page.

Thanks.

Hi @Kristin Fernandes

The framework is still unable to find specific web elements on the MAS login page. I have attached the logs along with the properties file and .bin file.
Could you please have a look and advise? Thank you.

Hi @Samvid Shivram

The MASPageLogin page should be the only file that needs to be updated in order to log into MAS 8.11. The IDs look correct to me so hopefully you've had a successful login after making the changes.

Thanks!

Hi @Kristin Fernandes

Thanks for the clarification.
Reading through the logs, I was able to find some of the class files and have updated the id/xpath of the elements (mainly username field, password field and continue button) as per the new login page for MAS 8.11. I have attached the modified files. Could you have a look and advise if there are more files to be updated?

Thank you.

Hi @Samvid Shivram

The automation framework supports MAS 8.10/Manage 8.6 and you're trying to use it against MAS 8.11/Manage 8.7, which it does not support. It's failing when trying to log in because the login screen changed between releases. If you want to use MAS 8.11, you would have to update the code in the framework to support the login screen.

Thank you.

Hi @Kristin Fernandes

I am facing an issue while running automation tests in Maximo Manage 9.1.266. The test fails to load the Maximo login page, and I am seeing the following errors in the log:
Log: <span style="color:#ff0000">SEVERE: ERROR: Failed to load Maximo Login Page.<span style="color:#ff0000">
Log: <span style="color:#ff0000">SEVERE: ERROR: Execution stopped for recorded test bin file: D:/Automation Workspace/Automation/tests\MyTestBins\test.bin<span style="color:#ff0000">
Log: java.lang.Exception: Failed to load Maximo Login Page.
Log:     at framework.selenium.Browser.testFail(Browser.java:157)
Log:     at framework.selenium.TpaeBrowser.logInAs(TpaeBrowser.java:811)
Log:     at framework.selenium.TpaeBrowser.logInAs(TpaeBrowser.java:741)
Log:     at framework.selenium.Browser.logIn(Browser.java:487)
Log:     at tests.testdriver.TestDriver.processEvent(TestDriver.java:1644)
Log:     at tests.testdriver.TestDriver.processTestFileLineByLine(TestDriver.java:1385)
Log:     at tests.testdriver.TestDriver.Driver(TestDriver.java:515)
Log:     at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Log:     at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
Log:     at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
Log:     at java.base/java.lang.reflect.Method.invoke(Method.java:568)
Log:     at org.testng.internal.invokers.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:139)
Log:     at org.testng.internal.invokers.TestInvoker.invokeMethod(TestInvoker.java:677)
Log:     at org.testng.internal.invokers.TestInvoker.invokeTestMethod(TestInvoker.java:221)
Log:     at org.testng.internal.invokers.MethodRunner.runInSequence(MethodRunner.java:50)
Log:     at org.testng.internal.invokers.TestInvoker$MethodInvocationAgent.invoke(TestInvoker.java:969)
Log:     at org.testng.internal.invokers.TestInvoker.invokeTestMethods(TestInvoker.java:194)
Log:     at org.testng.internal.invokers.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:148)
Log:     at org.testng.internal.invokers.TestMethodWorker.run(TestMethodWorker.java:128)
Log:     at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
Log:     at org.testng.TestRunner.privateRun(TestRunner.java:829)
Log:     at org.testng.TestRunner.run(TestRunner.java:602)
Log:     at org.testng.SuiteRunner.runTest(SuiteRunner.java:437)
Log:     at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:431)
Log:     at org.testng.SuiteRunner.privateRun(SuiteRunner.java:391)
Log:     at org.testng.SuiteRunner.run(SuiteRunner.java:330)
Log:     at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
Log:     at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:95)
Log:     at org.testng.TestNG.runSuitesSequentially(TestNG.java:1256)
Log:     at org.testng.TestNG.runSuitesLocally(TestNG.java:1176)
Log:     at org.testng.TestNG.runSuites(TestNG.java:1099)
Log:     at org.testng.TestNG.run(TestNG.java:1067)
Log:     at org.testng.remote.AbstractRemoteTestNG.run(AbstractRemoteTestNG.java:115)
Log:     at org.testng.remote.RemoteTestNG.initAndRun(RemoteTestNG.java:293)
Log:     at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:91)
Log: <span style="color:#ff0000">SEVERE: Resetting browser due to test failure<span style="color:#ff0000">
Log: <span style="color:#ff0000">SEVERE: TEST FAILED<span style="color:#ff0000">

For reference, I am using the following change in the login page class (TpaePageLogin) for the username field:
public TpaePageLogin(Browser br) {
    browser = br;
    prodNameXpath = "//input[@placeholder=\"Enter your username\"]";
}
I wanted to check if you have any suggestions or guidance on what might be causing this issue and how to resolve it. Any help would be greatly appreciated.

Thanks.

Hi @Samvid Shivram

Happy to hear it's working! 

There is no release planned for MAS 8.11; the next release will be for MAS 9.0.

Thanks.

Hi @Kristin Fernandes

Many thanks! After updating the line 25 in Page.java with a relevant web element and couple of other file changes, I was able to successfully execute a test case. Do we have a time lead for Test Automation Support for MAS 8.11? Looking forward to your reply. 

Hi @Samvid Shivram

Please remember that you are trying to use the framework on an unsupported version of MAS. We offer support via our community for the supported version only. The community can be found here: https://community.ibm.com/community/user/asset-facilities/viewdocument/ibm-maximo-test-automation-framewor

But since I can quickly answer your question I'll provide help with this one. If you go to Automation/framework/Page.java, you need to update line 25 to correctly reflect the login page.

Thanks.

Hi @Kristin Fernandes

The framework is still unable to find specific web elements on the MAS login page. I have attached the logs along with the properties file and .bin file.
Could you please have a look and advise? Thank you.

Hi @Samvid Shivram

The MASPageLogin page should be the only file that needs to be updated in order to log into MAS 8.11. The IDs look correct to me so hopefully you've had a successful login after making the changes.

Thanks!

Hi @Kristin Fernandes

Thanks for the clarification.
Reading through the logs, I was able to find some of the class files and have updated the id/xpath of the elements (mainly username field, password field and continue button) as per the new login page for MAS 8.11. I have attached the modified files. Could you have a look and advise if there are more files to be updated?

Thank you.

Hi @Samvid Shivram

The automation framework supports MAS 8.10/Manage 8.6 and you're trying to use it against MAS 8.11/Manage 8.7, which it does not support. It's failing when trying to log in because the login screen changed between releases. If you want to use MAS 8.11, you would have to update the code in the framework to support the login screen.

Thank you.

Mohd,

FYI the Maximo Test Automation Framework for v9.1 is not available yet. I followed up with IBM Product Management last week and it should be released soon as they work on resolving an issue is what I was told.

Hi @Kristin Fernandes

I am facing an issue while running automation tests in Maximo Manage 9.1.266. The test fails to load the Maximo login page, and I am seeing the following errors in the log:
Log: <span style="color:#ff0000">SEVERE: ERROR: Failed to load Maximo Login Page.<span style="color:#ff0000">
Log: <span style="color:#ff0000">SEVERE: ERROR: Execution stopped for recorded test bin file: D:/Automation Workspace/Automation/tests\MyTestBins\test.bin<span style="color:#ff0000">
Log: java.lang.Exception: Failed to load Maximo Login Page.
Log:     at framework.selenium.Browser.testFail(Browser.java:157)
Log:     at framework.selenium.TpaeBrowser.logInAs(TpaeBrowser.java:811)
Log:     at framework.selenium.TpaeBrowser.logInAs(TpaeBrowser.java:741)
Log:     at framework.selenium.Browser.logIn(Browser.java:487)
Log:     at tests.testdriver.TestDriver.processEvent(TestDriver.java:1644)
Log:     at tests.testdriver.TestDriver.processTestFileLineByLine(TestDriver.java:1385)
Log:     at tests.testdriver.TestDriver.Driver(TestDriver.java:515)
Log:     at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Log:     at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
Log:     at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
Log:     at java.base/java.lang.reflect.Method.invoke(Method.java:568)
Log:     at org.testng.internal.invokers.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:139)
Log:     at org.testng.internal.invokers.TestInvoker.invokeMethod(TestInvoker.java:677)
Log:     at org.testng.internal.invokers.TestInvoker.invokeTestMethod(TestInvoker.java:221)
Log:     at org.testng.internal.invokers.MethodRunner.runInSequence(MethodRunner.java:50)
Log:     at org.testng.internal.invokers.TestInvoker$MethodInvocationAgent.invoke(TestInvoker.java:969)
Log:     at org.testng.internal.invokers.TestInvoker.invokeTestMethods(TestInvoker.java:194)
Log:     at org.testng.internal.invokers.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:148)
Log:     at org.testng.internal.invokers.TestMethodWorker.run(TestMethodWorker.java:128)
Log:     at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
Log:     at org.testng.TestRunner.privateRun(TestRunner.java:829)
Log:     at org.testng.TestRunner.run(TestRunner.java:602)
Log:     at org.testng.SuiteRunner.runTest(SuiteRunner.java:437)
Log:     at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:431)
Log:     at org.testng.SuiteRunner.privateRun(SuiteRunner.java:391)
Log:     at org.testng.SuiteRunner.run(SuiteRunner.java:330)
Log:     at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
Log:     at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:95)
Log:     at org.testng.TestNG.runSuitesSequentially(TestNG.java:1256)
Log:     at org.testng.TestNG.runSuitesLocally(TestNG.java:1176)
Log:     at org.testng.TestNG.runSuites(TestNG.java:1099)
Log:     at org.testng.TestNG.run(TestNG.java:1067)
Log:     at org.testng.remote.AbstractRemoteTestNG.run(AbstractRemoteTestNG.java:115)
Log:     at org.testng.remote.RemoteTestNG.initAndRun(RemoteTestNG.java:293)
Log:     at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:91)
Log: <span style="color:#ff0000">SEVERE: Resetting browser due to test failure<span style="color:#ff0000">
Log: <span style="color:#ff0000">SEVERE: TEST FAILED<span style="color:#ff0000">

For reference, I am using the following change in the login page class (TpaePageLogin) for the username field:
public TpaePageLogin(Browser br) {
    browser = br;
    prodNameXpath = "//input[@placeholder=\"Enter your username\"]";
}
I wanted to check if you have any suggestions or guidance on what might be causing this issue and how to resolve it. Any help would be greatly appreciated.

Thanks.

Hi @Samvid Shivram

Happy to hear it's working! 

There is no release planned for MAS 8.11; the next release will be for MAS 9.0.

Thanks.

Hi @Kristin Fernandes

Many thanks! After updating the line 25 in Page.java with a relevant web element and couple of other file changes, I was able to successfully execute a test case. Do we have a time lead for Test Automation Support for MAS 8.11? Looking forward to your reply. 

Hi @Samvid Shivram

Please remember that you are trying to use the framework on an unsupported version of MAS. We offer support via our community for the supported version only. The community can be found here: https://community.ibm.com/community/user/asset-facilities/viewdocument/ibm-maximo-test-automation-framewor

But since I can quickly answer your question I'll provide help with this one. If you go to Automation/framework/Page.java, you need to update line 25 to correctly reflect the login page.

Thanks.

Hi @Kristin Fernandes

The framework is still unable to find specific web elements on the MAS login page. I have attached the logs along with the properties file and .bin file.
Could you please have a look and advise? Thank you.

Hi @Samvid Shivram

The MASPageLogin page should be the only file that needs to be updated in order to log into MAS 8.11. The IDs look correct to me so hopefully you've had a successful login after making the changes.

Thanks!

Hi @Kristin Fernandes

Thanks for the clarification.
Reading through the logs, I was able to find some of the class files and have updated the id/xpath of the elements (mainly username field, password field and continue button) as per the new login page for MAS 8.11. I have attached the modified files. Could you have a look and advise if there are more files to be updated?

Thank you.

Hi @Samvid Shivram

The automation framework supports MAS 8.10/Manage 8.6 and you're trying to use it against MAS 8.11/Manage 8.7, which it does not support. It's failing when trying to log in because the login screen changed between releases. If you want to use MAS 8.11, you would have to update the code in the framework to support the login screen.

Thank you.