This test depends on the base URI of the test environment, despite it going to some lengths to avoid this.

The use of p:resolve-uri('test') in

      <p:string-replace match="para[@class]/text()">
	<p:with-option name="replace"
		       select="concat('&quot;',p:resolve-uri('test'),'&quot;')"/>
      </p:string-replace>

is a compile-time constant based on the base URI of the test file.  Even if the test were written as:

      <p:string-replace match="para[@class]/text()">
	<p:with-option name="replace"
		       select="'p:resolve-uri(''test'')')"/>
      </p:string-replace>

then p:string-replace would evaluate 'replace' as the XPath expression

p:resolve-uri('test')

with a static base URI as "the base URI of the element on which the expression occurs" i.e. that of p:with-option.

Either way, the resolved URI has no relationship to the base URI of the document on the source port.