`file_serial` doesn't work for cucumber tests

[Propfend]

I don't know why but the file_serial doesn't work for cucumber-rs tests. Tests handler:

#[tokio::test]
#[file_serial(balancer, path => "/home/debian/paddler/src/tests/integration/balancer.rs")]
pub async fn run_cucumber_tests() {
    PaddlerWorld::cucumber()
        .run("src/tests/integration/features/balancer.feature")
        .await;
}

Even telling the path of the file, they are run asynchronously and both content are deleted.

[palfrey]

I don't know why but the file_serial doesn't work for cucumber-rs tests. Tests handler:

#[tokio::test]
#[file_serial(balancer, path => "/home/debian/paddler/src/tests/integration/balancer.rs")]
pub async fn run_cucumber_tests() {
PaddlerWorld::cucumber()
.run("src/tests/integration/features/balancer.feature")
.await;
}

Even telling the path of the file, they are run asynchronously and both content are deleted.

So the docs for file_serial don't make this entirely clear (and that should get fixed at some point), but the path is meant to be a path to a file that file_serial can use to record the locking info, it shouldn't already exist. The default path is derived from an OS-specific temp directory plus the key.

Do you have the same key value for your tests? Tests with a key in common (or no key at all) will run in serial, but different keys can run in parallel.

[Propfend]

Do you have the same key value for your tests? Tests with a key in common (or no key at all) will run in serial, but different keys can run in parallel.

Yes, im running both files with:

#[file_serial(key, path => "./info")]

And it doesn't work with no keys at all also:

#[file_serial(path => "./info")]

[palfrey]

I'm still not sure about this one. I was wondering about if it was to do with relative v.s. absolute paths maybe? #143 adds a debug statement documenting the absolute path a relative path gets converted to, and it might be your different tests are getting different absolute paths. Hard to tell without seeing actual code samples!