<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Cucumber with Appian JAR Methods Causing Page Load Issues in Jenkins</title><link>https://community.appian.com/discussions/f/new-to-appian/38752/cucumber-with-appian-jar-methods-causing-page-load-issues-in-jenkins</link><description>Scripts work fine in headless mode when I run them locally. But in Jenkins, the login page doesn&amp;#39;t load fully, and the &amp;#39;Sign In&amp;#39; button is missing so it throws an error when i use Appian 24.3 jar methods but the scripts running fine with page xpaths.</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Cucumber with Appian JAR Methods Causing Page Load Issues in Jenkins</title><link>https://community.appian.com/thread/146459?ContentTypeID=1</link><pubDate>Sat, 22 Mar 2025 08:39:11 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:cd1978ae-7840-48e4-9511-8553d3749514</guid><dc:creator>slpfrsly4j632080</dc:creator><description>&lt;p&gt;When running Cucumber tests with Appian JAR methods in a Jenkins pipeline, users may encounter page load issues that affect test execution. This can be due to improper synchronization &lt;span style="color:#000000;"&gt;&lt;a style="color:#000000;" href="https://codicefiscaleonline.info/"&gt;codice fiscale online&lt;/a&gt;&lt;/span&gt;&amp;nbsp;between test steps and the Appian application&amp;rsquo;s dynamic content rendering.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Cucumber with Appian JAR Methods Causing Page Load Issues in Jenkins</title><link>https://community.appian.com/thread/146457?ContentTypeID=1</link><pubDate>Sat, 22 Mar 2025 06:35:28 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:9a8b38c5-9aaa-4308-aacb-84187319b820</guid><dc:creator>kapilsharma</dc:creator><description>&lt;p&gt;Hi &lt;a href="/members/nalinit0001"&gt;nalini.tatiparthi@ehi.com&lt;/a&gt; ,&lt;br /&gt;&lt;br /&gt;I&amp;#39;m not sure if that would be the exact reason behind this but I would like to suggest that can you try the following:&lt;br /&gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Run the test in non-headless mode on Jenkins.&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Use driver.getPageSource() in Jenkins to check if the full HTML is being loaded.&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Try Appian JAR methods with debug logs enabled.&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Check Jenkins environment logs for any rendering errors.&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; The Appian JAR might be trying to interact before the elements are fully loaded. Use explicit waits before interacting with the &amp;quot;Sign In&amp;quot; button.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>