Schema Validation issues. Not ending launch

[dantench]

In our suite we have been using the following:

pm.test("Validate schema 2", ()=> { pm.response.to.have.jsonSchema(JSON.parse(pm.collectionVariables.get("schema"))); });

In ReportPortal this doesn't seem to validate/result in an 'finish' result.

Changing to:

pm.test("Validate schema 1", function() { pm.expect(tv4.validate(pm.response.json(),((JSON.parse(pm.collectionVariables.get("schema"))),true,true))).to.be.true; });

Then frustratingly when removing "Validate Schema 2" ... it also then doesn't work for "Validate Schema 1" though it did before... so something somewhere isn't right when it comes to validating schemas.

Incidently, postman itself has no issues with either:

[dantench]

Okay...... so on more playing this is actually a different issue :)

//Response time validation
if (!pm.collectionVariables.has("skipResponseTimeValidation")) {
    var responseTime = (pm.environment.has("responseTimeThreshold") ? pm.environment.get("responseTimeThreshold") : 500);
    pm.test("Response time is less than 500ms", function () {
        console.log(parseInt(responseTime));
		pm.expect(pm.response.responseTime).to.be.below(parseInt(responseTime));
    });
}

//JSON and Content-type validation
if (!pm.collectionVariables.has("skipContentTypeValidation")) {
    pm.test("Verify Response is JSON & validate Content-Type ", function () {
        pm.response.to.be.json;
        pm.expect((pm.response.headers.get("Content-Type")).replace(/\s/g, "")).to.eql("application/json;charset=UTF-8");
    });
} 

^ this caused the issue, where the below was set:

pm.collectionVariables.set("skipContentTypeValidation"); pm.collectionVariables.set("skipResponseTimeValidation");

The tests would still 'run' ( according to report portal ) and wouldn't close out. I think this is an extension of: #65 because report portal doesn't recognise a test wasn't completed/skipped.

Changing this to:

//Response time validation
if (pm.collectionVariables.has("skipResponseTimeValidation")) {
    var responseTime = (pm.environment.has("responseTimeThreshold") ? pm.environment.get("responseTimeThreshold") : 500);
    pm.test.skip("Response time is less than 500ms", function () {
        console.log("Skip Response Time Validation");
		pm.expect(pm.response.responseTime).to.be.below(parseInt(responseTime));
    })
}
else {
    pm.test("Response time is less than 500ms", function () {
        var responseTime = (pm.environment.has("responseTimeThreshold") ? pm.environment.get("responseTimeThreshold") : 500);
        console.log("Skip Response Time Validation");
		pm.expect(pm.response.responseTime).to.be.below(parseInt(responseTime));
    })
}


//JSON and Content-type validation
if (pm.collectionVariables.has("skipContentTypeValidation")) {
    pm.test.skip("Verify Response is JSON & validate Content-Type ", function () {
        console.log("Skip Content Type Validation");
        pm.response.to.be.json;
        pm.expect((pm.response.headers.get("Content-Type")).replace(/\s/g, "")).to.eql("application/json;charset=UTF-8");
    });
}
else {
    pm.test("Verify Response is JSON & validate Content-Type ", function () {
        pm.response.to.be.json;
        pm.expect((pm.response.headers.get("Content-Type")).replace(/\s/g, "")).to.eql("application/json;charset=UTF-8");
    });
}

Solved this problem.

[dantench]

I think this is ultimatly caused by : #64

[dgosantos89]

#94