<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Thu Feb 08 23:10:25 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>FOLIO Jira</title>
    <link>https://folio-org.atlassian.net</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>1001.0.0-SNAPSHOT</version>
        <build-number>100246</build-number>
        <build-date>07-02-2024</build-date>
    </build-info>

<item>
            <title>[FOLIO-1043] integrate ui-testing with PR</title>
                <link>https://folio-org.atlassian.net/browse/FOLIO-1043</link>
                <project id="10290" key="FOLIO">FOLIO</project>
                    <description>&lt;p&gt;The idea is to speed up construction of the test system (maybe re-use the same system and upgrade selected components only) and the test run so it is possible to integrate it with the PR.&lt;/p&gt;

&lt;p&gt;1. &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f9abc1eb45b2e007453f423&quot; class=&quot;user-hover&quot; rel=&quot;5f9abc1eb45b2e007453f423&quot; data-account-id=&quot;5f9abc1eb45b2e007453f423&quot; accountid=&quot;5f9abc1eb45b2e007453f423&quot; rel=&quot;noreferrer&quot;&gt;John Malconian&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5c706fbb47a54a6728e59df2&quot; class=&quot;user-hover&quot; rel=&quot;5c706fbb47a54a6728e59df2&quot; data-account-id=&quot;5c706fbb47a54a6728e59df2&quot; accountid=&quot;5c706fbb47a54a6728e59df2&quot; rel=&quot;noreferrer&quot;&gt;Wayne Schneider&lt;/a&gt; Describe the approach&lt;/p&gt;</description>
                <environment></environment>
        <key id="80538">FOLIO-1043</key>
            <summary>integrate ui-testing with PR</summary>
                <type id="10006" iconUrl="https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10307?size=medium">Umbrella</type>
                                            <priority id="10002" iconUrl="https://dev.folio.org/assets/jira-priority/jira-p3.svg">P3</priority>
                        <status id="6" iconUrl="https://folio-org.atlassian.net/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10001">Duplicate</resolution>
                                                        <assignee accountid="5f9abc1eb45b2e007453f423">John Malconian</assignee>
                                                                <reporter accountid="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d">Jakub Skoczen</reporter>
                                    <labels>
                            <label>build-release</label>
                            <label>ci</label>
                            <label>devops</label>
                            <label>madrid</label>
                            <label>sprint31</label>
                            <label>sprint32</label>
                            <label>sprint33</label>
                            <label>sprint34</label>
                            <label>sprint36</label>
                            <label>sprint37</label>
                            <label>sprint38</label>
                            <label>sprint39</label>
                            <label>sprint40</label>
                            <label>sprint41</label>
                            <label>sprint42</label>
                            <label>sprint43</label>
                            <label>sprint44</label>
                            <label>sprint45</label>
                    </labels>
                <created>Tue, 30 Jan 2018 14:13:44 +0000</created>
                <updated>Wed, 20 Mar 2019 15:07:49 +0000</updated>
                            <resolved>Wed, 20 Mar 2019 15:07:49 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>9</watches>
                                                    <timespent seconds="633600">4 weeks, 2 days</timespent>
                                <comments>
                                                            <comment id="189554" author="5f9abc1eb45b2e007453f423" created="Wed, 31 Jan 2018 13:34:08 +0000"  >&lt;p&gt;The idea, at least initially, is to run the UI regression test suite as part of a PR for any of the Stripes and UI-based repositories,  This would be orchestrated by Jenkins.   The UI test suite would be run against a pre-built FOLIO backend stack that is rebuilt daily.   In order to set a known, good, baseline,  the backend stack that is used will be an instance of &apos;folio-snapshot-stable&apos;.   For each PR,  the CI will create a tenant on the backend, load a subset of data for that tenant, build a stripes platform which will include the changes for the UI component being testing.    The UI regression test suite (or a portion of it) will be run against that stripes build.  If all tests pass,  the PR will be available to merge to master.    If any tests fail,  the developer will be notified and the pipeline stops until the issue is fixed and a subsequent PR is run and passes. &lt;/p&gt;</comment>
                                                            <comment id="189555" author="5c706fbb47a54a6728e59df2" created="Wed, 7 Feb 2018 15:14:26 +0000"  >&lt;p&gt;Process document: &lt;a href=&quot;https://docs.google.com/document/d/1YcHV7Dx-LMGckyLVPu3izLtgfrSR-0rFxNsLbsYuYfI&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://docs.google.com/document/d/1YcHV7Dx-LMGckyLVPu3izLtgfrSR-0rFxNsLbsYuYfI&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="189558" author="5f9abc1eb45b2e007453f423" created="Tue, 13 Mar 2018 20:10:57 +0000"  >&lt;p&gt;There are two outstanding issues that need to be added for this to be completed:&lt;/p&gt;

&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;add the ability to deploy new/updated modules via the install endpoint (see also folio-1111)&lt;/li&gt;
	&lt;li&gt;add sample user data to the tenant instance&lt;/li&gt;
&lt;/ul&gt;
</comment>
                                                            <comment id="189559" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Wed, 14 Mar 2018 13:16:13 +0000"  >&lt;p&gt;We discussed that it would make sense to enable that for ui-users first, sometime next week.&lt;/p&gt;</comment>
                                                            <comment id="189560" author="5f9abc1eb45b2e007453f423" created="Fri, 30 Mar 2018 17:31:21 +0000"  >&lt;p&gt;Couple of things that are holding back this implementation:&lt;/p&gt;

&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;We need a working folio-snapshot-stable.   Last &quot;stable&quot; build (e.g passed regression tests was March 20.&lt;/li&gt;
	&lt;li&gt;
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;RMB-154&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/RMB-154&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Investigate postgresql connection pool&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            RMB-154
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
.  This is causing issues with more than 3-4 tenants&lt;/li&gt;
&lt;/ul&gt;
</comment>
                                                            <comment id="189562" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Wed, 11 Apr 2018 13:28:36 +0000"  >&lt;p&gt;We have discussed two things:&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;putting the lin yarn.lock on the Jenkins build page&lt;/li&gt;
	&lt;li&gt;running the build in the DEBUG mode (for informative nightmare errors)&lt;/li&gt;
&lt;/ul&gt;
</comment>
                                                            <comment id="189563" author="5f9abc1eb45b2e007453f423" created="Wed, 11 Apr 2018 15:38:31 +0000"  >&lt;p&gt;Test implementation exists on branch folio-1043-test of ui-users.   There seems to be a discrepancy in the number of test failures compared to the nightly tests against folio-snapshot during roughly the same period.    Some things to implement in an attempt to drill down into the cause of the discrepancy: &lt;/p&gt;

&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;&apos;link&apos; in the repository code in the ui-testing platform&lt;/li&gt;
	&lt;li&gt;remove the node_modules directory in the repository code after the initial &apos;yarn install&apos;&lt;/li&gt;
	&lt;li&gt;publish the yarn.lock file with the build that is generated in folio-testing-platform.&lt;/li&gt;
&lt;/ul&gt;
</comment>
                                                            <comment id="189565" author="5f9abc1eb45b2e007453f423" created="Thu, 12 Apr 2018 20:09:04 +0000"  >&lt;p&gt;After fiddling around more with &apos;yarn linking&apos; and adding the mod-auth-demo-users role to the tenant configuration,  the last run produced only three failures.  &lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://jenkins-aws.indexdata.com/job/folio-org/job/ui-users/job/folio-1043-test/88/UI_Regression_Test_Report/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://jenkins-aws.indexdata.com/job/folio-org/job/ui-users/job/folio-1043-test/88/UI_Regression_Test_Report/&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="189567" author="5f9abc1eb45b2e007453f423" created="Thu, 12 Apr 2018 20:24:48 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5bffed5e2434bf3a1a91d37a&quot; class=&quot;user-hover&quot; rel=&quot;5bffed5e2434bf3a1a91d37a&quot; data-account-id=&quot;5bffed5e2434bf3a1a91d37a&quot; accountid=&quot;5bffed5e2434bf3a1a91d37a&quot; rel=&quot;noreferrer&quot;&gt;Niels Erik Nielsen&lt;/a&gt; has pointed out that a couple of the regression tests rely on the existence of the &apos;diku_admin&apos; user.   However,  the test is run against a different tenant/tenant admin.    &lt;/p&gt;</comment>
                                                            <comment id="189569" author="5dcd5f6b97a0a20c664045ee" created="Thu, 12 Apr 2018 20:37:43 +0000"  >&lt;p&gt;It looks like the tests are expecting a certain title to be in the codex search, and it can&apos;t find any active users.  Are we loading the same users and codex titles as in &lt;a href=&quot;http://folio-testing.aws.indexdata.com/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;http://folio-testing.aws.indexdata.com/&lt;/a&gt; ?&lt;/p&gt;</comment>
                                                            <comment id="189571" author="5f9abc1eb45b2e007453f423" created="Thu, 12 Apr 2018 20:39:59 +0000"  >&lt;p&gt;The codex search failure fails because the title, Arctic A-Z, exists only in a larger sample inventory data set that is not loaded for PR tests where only a minimal dataset is loaded.   I&apos;d rather not have to load the larger dataset for each tenant/PR.     Perhaps we can change the behavior of this test somehow? &lt;/p&gt;</comment>
                                                            <comment id="189572" author="5f9abc1eb45b2e007453f423" created="Thu, 12 Apr 2018 20:42:23 +0000"  >&lt;p&gt;For example, the &quot;New POPS&quot; title is included in the minimal dataset so it would be found in all tenant instances (except it wouldn&apos;t be the first title found in instances with the larger dataset included. &lt;/p&gt;</comment>
                                                            <comment id="189574" author="5dcd5f6b97a0a20c664045ee" created="Thu, 12 Apr 2018 20:46:48 +0000"  >&lt;p&gt;Ok-- this sounds good.&lt;/p&gt;</comment>
                                                            <comment id="189575" author="5dcd5f6b97a0a20c664045ee" created="Thu, 12 Apr 2018 21:46:18 +0000"  >&lt;p&gt;I changed the search term in the codex search test to &quot;POPs in Marine Mammals&quot;.   &lt;/p&gt;</comment>
                                                            <comment id="189577" author="5f9abc1eb45b2e007453f423" created="Fri, 13 Apr 2018 18:49:24 +0000"  >&lt;p&gt;It appears all issues related to passing/failing UI tests have been worked out.  I&apos;ve also enabled publishing of yarn.lock files in Jenkins (they can be downloaded/viewed per job).  I&apos;ve been able to run the full UI regression suite without error in testing.    I intend to implement full-stack PR-based regression testing on two repositories - ui-users and ui-inventory - on Monday morning.  We&apos;ll see how it goes and make adjustments from there.    &lt;/p&gt;</comment>
                                                            <comment id="189578" author="5f9abc1eb45b2e007453f423" created="Tue, 1 May 2018 16:34:08 +0000"  >&lt;p&gt;I&apos;ve implemented a couple of new features into CI.   &lt;/p&gt;

&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;PR-based regression tests are configurable in the project&apos;s Jenkinsfile:&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;runRegression = &apos;partial&apos; - Run module&apos;s UI regression tests only. &lt;br/&gt;
runRegression = &apos;full&apos; - Run full UI regression test suite. &lt;br/&gt;
runRegression = &apos;none&apos; - Do not run UI regression tests (this is the default when not explicitly configured. &lt;/p&gt;

&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;Regression testing is skipped if there is a module dependency mismatch.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Currently,  the &apos;ui-inventory&apos; and &apos;ui-users&apos; repositories are configured with &quot;runRegression = &apos;partial&apos;&quot;.   I&apos;ll enable regression testing for additional repositories gradually.  &lt;/p&gt;</comment>
                                                            <comment id="189580" author="5bffed5e2434bf3a1a91d37a" created="Tue, 1 May 2018 19:52:34 +0000"  >&lt;p&gt;Cool!&lt;/p&gt;</comment>
                                                            <comment id="189582" author="5f9abc1eb45b2e007453f423" created="Fri, 11 May 2018 14:07:45 +0000"  >&lt;p&gt;Currently,  when a PR submitted for regression testing,  the module that is tested is linked into &apos;folio-testing-platform&apos; and the whole stripes platform is built and posted to Okapi.    I&apos;m thinking it would be more efficient to test the module with a more barebones stripes platform that consists only of the module being tested along with common stripes dependencies (stripes-core, stripes-components) and enabling only the backend modules that are explicitly specified as okapi interface dependencies.      &lt;/p&gt;</comment>
                                                            <comment id="189584" author="5f8314dfbdef80006f6f572d" created="Fri, 11 May 2018 14:23:41 +0000"  >&lt;p&gt;That would be great .. It would also check that the dependencies are right.&lt;/p&gt;</comment>
                                                            <comment id="189585" author="557058:624212b9-5938-4e3b-84c6-8c8a8db84996" created="Fri, 11 May 2018 16:06:51 +0000"  >&lt;blockquote&gt;
&lt;p&gt;I&apos;m thinking it would be more efficient to test the module with a more barebones stripes platform that consists only of the module being tested&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f9abc1eb45b2e007453f423&quot; class=&quot;user-hover&quot; rel=&quot;5f9abc1eb45b2e007453f423&quot; data-account-id=&quot;5f9abc1eb45b2e007453f423&quot; accountid=&quot;5f9abc1eb45b2e007453f423&quot; rel=&quot;noreferrer&quot;&gt;John Malconian&lt;/a&gt;, Stripes CLI does exactly this.  From the app module&apos;s directory, run:&lt;/p&gt;

&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
stripes test nightmare
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</comment>
                                                            <comment id="189587" author="5f9abc1eb45b2e007453f423" created="Fri, 1 Jun 2018 14:23:03 +0000"  >&lt;p&gt;Implemented &apos;partial&apos; regression tests for PRs on ui-requests and ui-checkout projects.    In total,  PR partial regression testing is enabled now for ui-users, ui-inventory, ui-requests, and ui-checkout.    Correct me if I&apos;m wrong &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5bffed5e2434bf3a1a91d37a&quot; class=&quot;user-hover&quot; rel=&quot;5bffed5e2434bf3a1a91d37a&quot; data-account-id=&quot;5bffed5e2434bf3a1a91d37a&quot; accountid=&quot;5bffed5e2434bf3a1a91d37a&quot; rel=&quot;noreferrer&quot;&gt;Niels Erik Nielsen&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5dcd5f6b97a0a20c664045ee&quot; class=&quot;user-hover&quot; rel=&quot;5dcd5f6b97a0a20c664045ee&quot; data-account-id=&quot;5dcd5f6b97a0a20c664045ee&quot; accountid=&quot;5dcd5f6b97a0a20c664045ee&quot; rel=&quot;noreferrer&quot;&gt;charles&lt;/a&gt;, but I don&apos;t think there are any other module specific test suites for any other UI module (ui-checkin, for example).   So for all other UI modules,  we either need to enable full regression tests for PRs or not enable any tests at all?&lt;/p&gt;</comment>
                                                            <comment id="189589" author="5bffed5e2434bf3a1a91d37a" created="Fri, 1 Jun 2018 17:32:58 +0000"  >&lt;p&gt;Right &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f9abc1eb45b2e007453f423&quot; class=&quot;user-hover&quot; rel=&quot;5f9abc1eb45b2e007453f423&quot; data-account-id=&quot;5f9abc1eb45b2e007453f423&quot; accountid=&quot;5f9abc1eb45b2e007453f423&quot; rel=&quot;noreferrer&quot;&gt;John Malconian&lt;/a&gt; Personally I think non-core module should only run their own tests on the PR. If they don&apos;t have any they will not run any.&lt;/p&gt;

&lt;p&gt;The developer should optimally still run relevant cross-module tests (typically &apos;test-exercise&apos;) or &amp;#8211; if that&apos;s simpler &amp;#8211; the entire suite, locally.&lt;/p&gt;</comment>
                                                            <comment id="189591" author="5bffed5e2434bf3a1a91d37a" created="Fri, 1 Jun 2018 17:36:47 +0000"  >&lt;p&gt;Regarding running a platform with only the module being tested: &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1043?focusedCommentId=189585&amp;amp;page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://folio-org.atlassian.net/browse/FOLIO-1043?focusedCommentId=189585&amp;amp;page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&lt;/a&gt;  &lt;/p&gt;

&lt;p&gt;I know I&apos;ve said it elsewhere, but just a note for the record here as well:&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;Some tests go out to find sample data for testing  in other modules.&lt;/li&gt;
	&lt;li&gt;Some modules invoke other modules.&lt;/li&gt;
&lt;/ul&gt;
</comment>
                                                            <comment id="189592" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Wed, 6 Jun 2018 14:57:52 +0000"  >&lt;p&gt;We have discussed an alternative approach to yarn linking whereby we specify the dependency of the package under test as the SHA1 of the Git commit. This can be done through a yarn command. The yarn.lock will be retrieved during the build process from a snapshot-stable URL (where it is already retain after each successful build).&lt;/p&gt;</comment>
                                                            <comment id="189595" author="5f9abc1eb45b2e007453f423" created="Tue, 26 Jun 2018 19:47:46 +0000"  >&lt;p&gt;Here is a summary of the latest changes: &lt;/p&gt;

&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;Instead of updating the package dependencies SHA1,  I opted to use &apos;yard add file: ...&apos; instead.   The branch that is getting tested and merged has already been cloned and the project has already undergone all the CI machinations in regards to versioning, etc.  It&apos;s effectively the same as using the git commit hash.&lt;/li&gt;
&lt;/ul&gt;


&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;I&apos;ve added the &apos;stripesPlatform&apos; Jenkinsfile config option.   &apos;stripesPlatform&apos; specifies the Stripes platform to use when building the webpack.    The default right now if this option is not specified is &apos;folio-testing-platform&apos;.   Other options currently are &apos;platform-core&apos;, &apos;folio-testing-platform&apos; and &apos;none&apos;.   When &apos;none&apos; is specified,  stripes-cli will build an &quot;app mode&quot; minimal bundle.   Currently, &apos;none&apos; has been configured for the stripes-core, stripes-components, and stripes-smart-components repos.    &apos;platform-core&apos; has been configured for ui-users, ui-inventory, ui-requests, and ui-checkout.   The rest are, therefore, still using &apos;folio-testing-plaform&apos;.  &apos;folio-testing-platform&apos; probably shouldn&apos;t be the long-term default,  but, for now, it was easiest in order to implement these changes.&lt;/li&gt;
&lt;/ul&gt;


&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;Use of the current yarn.lock from folio-snapshot-stable when building Stripes platform.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;I&apos;ve also learned to never specify &apos;NODE_OPTIONS=--max_old_space_size...&apos; globally.   I spent about 3 days trying to figure out why the regression tests wouldn&apos;t run after making the above changes that was due to this.  &lt;/p&gt;</comment>
                                                            <comment id="189597" author="557058:624212b9-5938-4e3b-84c6-8c8a8db84996" created="Wed, 27 Jun 2018 13:09:12 +0000"  >&lt;p&gt;FYI, I&apos;ve updated stripe-cli&apos;s own jenkinsfile platform to &apos;none&apos; as well.  Technically the CLI doesn&apos;t have anything to build in app mode, so I&apos;m wondering if we should introduce a platform value that does even less than &apos;none&apos;.&lt;/p&gt;

&lt;p&gt;At this point, do you need 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;STCLI-63&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/STCLI-63&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Support running tests against existing instance&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            STCLI-63
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 complete to invoke the tests?&lt;/p&gt;</comment>
                                                            <comment id="189599" author="5f9abc1eb45b2e007453f423" created="Mon, 23 Jul 2018 15:02:29 +0000"  >&lt;p&gt;Disable regression testing for PRs on ui-checkout, ui-requests, ui-users, and ui-inventory.  Blocked by 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-1338&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1338&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Regression tests fail consistently in PRs&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            FOLIO-1338
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 and 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-1312&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1312&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Intermittant ansible deployment errors during PRs&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            FOLIO-1312
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
.&lt;/p&gt;</comment>
                                                            <comment id="189601" author="63e2a2771b13d42998e4e706" created="Mon, 23 Jul 2018 16:01:30 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f9abc1eb45b2e007453f423&quot; class=&quot;user-hover&quot; rel=&quot;5f9abc1eb45b2e007453f423&quot; data-account-id=&quot;5f9abc1eb45b2e007453f423&quot; accountid=&quot;5f9abc1eb45b2e007453f423&quot; rel=&quot;noreferrer&quot;&gt;John Malconian&lt;/a&gt; Can you help me understand why running the tests has been completely disabled?&lt;/p&gt;</comment>
                                                            <comment id="189604" author="5f9abc1eb45b2e007453f423" created="Mon, 23 Jul 2018 16:43:17 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=63e2a2771b13d42998e4e706&quot; class=&quot;user-hover&quot; rel=&quot;63e2a2771b13d42998e4e706&quot; data-account-id=&quot;63e2a2771b13d42998e4e706&quot; accountid=&quot;63e2a2771b13d42998e4e706&quot; rel=&quot;noreferrer&quot;&gt;Marc Johnson&lt;/a&gt; - A combination of the systematic test failures in PRs that are not duplicated on the nightly tests as well as 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-1312&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1312&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Intermittant ansible deployment errors during PRs&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            FOLIO-1312
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 which is producing far too many failures that have nothing to with the actual code being tested. &lt;/p&gt;</comment>
                                                            <comment id="189606" author="5f9abc1eb45b2e007453f423" created="Tue, 31 Jul 2018 17:15:00 +0000"  >&lt;p&gt;Re-enabled regression testing for PRs for ui-checkout, ui-requests, ui-users, and ui-inventory,   In addition,  added module tests for ui-organization.   Will need to monitor for any signs of  
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-1312&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1312&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Intermittant ansible deployment errors during PRs&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            FOLIO-1312
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
. &lt;/p&gt;</comment>
                                                            <comment id="189607" author="5f9abc1eb45b2e007453f423" created="Tue, 7 Aug 2018 14:11:14 +0000"  >&lt;p&gt;Disable regression testing for PRs for ui-checkout, ui-requests, ui-users, and ui-inventory, and ui-organization until 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-1312&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1312&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Intermittant ansible deployment errors during PRs&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            FOLIO-1312
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 is resolved.  &lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                                                <inwardlinks description="is blocked by">
                                        <issuelink>
            <issuekey id="80585">FOLIO-1111</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="80623">FOLIO-1212</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="80752">FOLIO-1266</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="80691">FOLIO-1338</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="56884">RMB-154</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="44801">UIU-604</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="44802">UIU-605</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="80695">FOLIO-1270</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="80672">FOLIO-1312</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="65122">UICHKOUT-414</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10002">
                    <name>Duplicate</name>
                                            <outwardlinks description="duplicates">
                                        <issuelink>
            <issuekey id="80951">FOLIO-1577</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="80623">FOLIO-1212</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="80691">FOLIO-1338</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="80617">FOLIO-1204</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="53985">OKAPI-603</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="71313">STCLI-59</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="71314">STCLI-60</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="80542">FOLIO-1051</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="44801">UIU-604</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="44802">UIU-605</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="80481">FOLIO-1022</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="80540">FOLIO-1050</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="36914">UITEST-16</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="44640">UIU-400</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="10655">UXPROD-1055</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="10659">UXPROD-1059</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10000" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummarycf">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10057" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Development Team</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10144"><![CDATA[Core: Platform]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|hzy9dz:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10020" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10024" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>[CHART] Date of First Response</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Wed, 31 Jan 2018 13:34:08 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10025" key="com.atlassian.jira.ext.charting:timeinstatus">
                        <customfieldname>[CHART] Time in Status</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                    </customfields>
    </item>
</channel>
</rss>