I'm working with a system that has several external system dependencies. These external systems are only hooked into certain SDLC environments (local, dev, qa, and prod). Due to these restrictions, I have put environment checks in place on my some of my protractor tests to determine which environment they are in before executing.
For example:
'Test A' is being run, but it is dependent on interacting with 'external system 1' which is only enabled for the QA environment. So if 'Test A' is being run in Local, Dev, or Prod then the test will fail with a message to the console using fail().
My question is... Is there a way to force the test to Pass or be Skipped with a message similar to using fail()? I'm trying to delineate between tests actually passing or failing cause of functionality and if the test was simply skipped due to environment dependencies in my reports.
I know you can technically "skip" tests when your use "fdescribe" or "fit" and the console will print out something similar to the below
Executed 1 of 25 specs (1 FAILED) (24 SKIPPED) in 18 secs.
How can I invoke that skipping capability from with my tests?