In unit tests we write MR programs and other things with //no-op
If we do the same thing we get the spark program success status as false because to collect program status we use SparkListener which listens on job status. It expects a job to run to report the status as successful or otherwise.
Find out if there is some other way to get job status from spark which can allow us to use //no=op programs in unit tests.
We might be able to do this by listening to the callback on spark user program run