Overview
FitNesse for Appian is a client-side tool that makes it easy to create automated tests on the Appian platform. Create test scripts that will run Appian as if a user was clicking through the application and filling out data. FitNesse for Appian includes easy instructions to get you started.
Note: Java 11 required for plugin version 23.4
Key Features & Functionality
With FitNesse for Appian, you can:
Reusable scripts can be written to:
I am using the latest version FitnesseForAppian-24.2.0 and I see the same exact error message "ERROR StatusLogger Reconfiguration failed: No configuration found for '30946e09' at 'null' in 'null'"."
It launches the browser window, and cursor is there in the browser address, but URL is not typed.
Anyone had luck getting past this error? need to help on this.
Error details:
ERROR StatusLogger Reconfiguration failed: No configuration found for '30946e09' at 'null' in 'null' java.lang.NullPointerException at com.appiancorp.ps.automatedtest.tempo.TempoLogin.waitForSitesLogoutLink(TempoLogin.java:109) at com.appiancorp.ps.automatedtest.tempo.TempoLogin.waitFor(TempoLogin.java:92) at com.appiancorp.ps.automatedtest.fixture.TempoFixture.logout(TempoFixture.java:161) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at fitnesse.slim.fixtureInteraction.SimpleInteraction.methodInvoke(SimpleInteraction.java:322) at fitnesse.slim.fixtureInteraction.SimpleInteraction.callMethod(SimpleInteraction.java:307) at fitnesse.slim.fixtureInteraction.SimpleInteraction.invokeMethod(SimpleInteraction.java:290) at fitnesse.slim.fixtureInteraction.SimpleInteraction.findAndInvoke(SimpleInteraction.java:217) at fitnesse.slim.MethodExecutor.findAndInvoke(MethodExecutor.java:18) at fitnesse.slim.FixtureMethodExecutor.execute(FixtureMethodExecutor.java:18) at fitnesse.slim.StatementExecutor.getMethodExecutionResult(StatementExecutor.java:139) at fitnesse.slim.StatementExecutor.call(StatementExecutor.java:112) at fitnesse.slim.instructions.CallAndOptionalAssignInstruction.executeInternal(CallAndOptionalAssignInstruction.java:30) at fitnesse.slim.instructions.Instruction.execute(Instruction.java:29) at fitnesse.slim.ListExecutor$Executive.executeStatement(ListExecutor.java:49) at fitnesse.slim.ListExecutor$Executive.executeStatements(ListExecutor.java:43) at fitnesse.slim.ListExecutor.execute(ListExecutor.java:85) at fitnesse.slim.SlimServer.executeInstructions(SlimServer.java:84) at fitnesse.slim.SlimServer.processOneSetOfInstructions(SlimServer.java:77) at fitnesse.slim.SlimServer.tryProcessInstructions(SlimServer.java:64) at fitnesse.slim.SlimServer.serve(SlimServer.java:49) at fitnesse.slim.SlimService.handle(SlimService.java:169) at fitnesse.slim.SlimService.acceptOne(SlimService.java:177) at fitnesse.slim.SlimService.accept(SlimService.java:139) at fitnesse.slim.SlimService.startWithFactory(SlimService.java:92) at fitnesse.slim.SlimService.main(SlimService.java:57)
The issue was resolved after the browser driver .exe files placed in lib/drivers folder.