Hi all, I have

testIsolation

set to true at a global level. I'd like certain describe blocks to run without

testIsolation

, so that I can run several

it

commands in sequence, each with an assertion. According to the docs, I can define

testIsolation

at a

describe

level. My interpretation is that is would apply to block only, but it doesn't appear to work like that, or perhaps I'm misunderstanding. Here's an example, for a given spec file

describe('Some tests', () => {

  describe('Test A', { testIsolation: false }, () => {
    it('C1: verifies something', () => {
      // run some assertion
    });
    
    it('C2: verifies something else', () => {
      // run some assertion
    });
  });
  
  describe('Test B', { testIsolation: false } () => {
    it('C3: verifies something', () => {
      // run some assertion
    });
    
    it('C4: verifies something else', () => {
      // run some assertion
    });
  });
});

In this case, I'd expect

testIsolation

to only be applicable to the "inner"

it

commands. That is, "Test A" and "Test B" would run in isolation of each other. In practice, I'm observing "Test B" doesn't clear the browser session, etc. Thanks!

As you are using Nested Describe its looking like a problem for you Try to check once by executing without Outer describe 'Some tests'

hah. let me try that

ok please look into this article. which may help you set some configurations if possible? as even long back I landed into the same problem https://wordpress.com/read/feeds/137922491/posts/4545179635

I thought that with Test Isolation enabled, Cypress resets the browser context before each test. Not after. So if its disabled, then its not going to clear up after itself. I thought this goes hand in hand with the principle of setting the state before each test, not relying on an after hook of a previous request that you don't know succeded or not. Same princple applies to test data. Your before should ensure that the state is correct. Not rely on a previous test clearing up after itself. https://docs.cypress.io/guides/core-concepts/test-isolation

@incalculable-rainbow-43330 I get a login screen with that link

Sorry please check this link then https://techkakani.wordpress.com/2023/02/10/handling-test-isolation-problem-for-nested-describe-after-cypress-12-update/

thank you @incalculable-rainbow-43330 ! I ended up adopting a similar solution... Kind of sucks any way, would hope it would be built-in 🙂

yah i think Cypress would have given it by default as false and if we want we can set it to True in that way there use to be no confusion, but it happened in other way 🙂 Good Luck