Running test files sequentially

[mohsen1]

I want each file (or describe block) runs and finish then next describe block starts running my tests in it. (isn't that default jasmine behavior?)

I have multiple files in my tests folder, here is my config file:

exports.config = {
    seleniumAddress: 'http://localhost:4444/wd/hub', // goes to profile
    specs: argv.f ? argv.f.split(' ') : ['protractor/tests/*Test.js'],

    baseUrl: config.base_url + '/platform/',

    jasmineNodeOpts: {
        showColors: true,
        defaultTimeoutInterval: 25000
    },

    onPrepare: function() {

When I pass argument to test runner to just test one file, it works perfect. I tried this for every file and it did work. Each file has one describe block. But when I don't pass the argument for test file to test all files, it fails. I put console.log statements to see which file is running first, but surprising all my console.logs was printed at the same time.

Does Protractor tries to run all files that matches the patters at the same time? How can I fix this?

[juliemr]

Protractor does not try to run all the files at the same time - You're probably seeing all of your console.log statements because all of the file are loaded before execution of any one test begins. Also, tests are asynchronous, which may be why you're getting console.log statements all at once (depending on where you put them).

[mohsen1]

Hi @juliemr,

Thank you for responding. Per my investigation in issue, it was my fault that I was putting describe and it methods next to each other in my tests. My tests used to look like this:

describe('things', function(){
   it('should do foo', function(){/*...*/})
   describe('a batch of other things to test', function(){ /*...*/});
}

Now that I've moved those it calls in their own describe block, it doesn't have that problem anymore.

describe('things', function(){
   describe('foo', function()
       it('should do foo', function(){/*...*/})
   });
   describe('a batch of other things to test', function(){ /*...*/});
}

I'm closing the issue because it's not Protractor's fault.