Forward compatibility for build history widget rewrite (#1557)

Co-authored-by: Tim Jacomb <[email protected]>

src/test/java/plugins/DescriptionSetterPluginTest.java

@@ -37,6 +37,6 @@ public void set_build_description_based_upon_build_log_file() {
  assertThat(find(by.css("div#description div")).getText(), is(equalTo(msg)));
 
  j.open();
- assertThat(find(by.css("#buildHistory .desc")).getText(), is(equalTo(msg)));
+ assertThat(find(by.css("#buildHistoryPage .desc, #buildHistoryPage .app-builds-container__item__description")).getText(), is(equalTo(msg)));
  }
 }

src/test/java/plugins/NodeLabelParameterPluginTest.java

@@ -511,7 +511,7 @@ public boolean matchesSafely(Build build) {
  private org.hamcrest.Matcher<String> isPending(String nodename) {
  return allOf(
  containsString("Job triggered without a valid online node, given where: " + nodename),
- containsString("pending")
+ containsStringIgnoringCase("Pending")
  );
  }
 
@@ -524,8 +524,8 @@ private String getPendingBuildText(Build build) {
  build.job.open();
 
  // pending message comes from the queue, and queue's maintenance is asynchronous to UI threads.
- // so if the original response doesn't contain it, we have to wait for the refersh of the build history.
+ // so if the original response doesn't contain it, we have to wait for the refresh of the build history.
  // so give it a bigger wait.
- return find(by.css("#buildHistory")).getText();
+ return find(by.css("#buildHistoryPage")).getText();
  }
 }