2020-01-31 10:08:40 -05:00
|
|
|
function assertInsideProxyZone() {
|
|
|
|
expect(Zone.current.name).toEqual('ProxyZone');
|
|
|
|
}
|
|
|
|
function assertInsideSyncDescribeZone() {
|
|
|
|
expect(Zone.current.name).toEqual('syncTestZone for jest.describe');
|
|
|
|
}
|
|
|
|
describe('describe', () => {
|
|
|
|
assertInsideSyncDescribeZone();
|
fix(zone.js): zone.js patch jest should handle done correctly (#36022)
`zone.js` supports jest `test.each()` methods, but it
introduces a bug, which is the `done()` function will not be handled correctly.
```
it('should work with done', done => {
// done will be undefined.
});
```
The reason is the logic of monkey patching `test` method is different from `jasmine` patch
// jasmine patch
```
return testBody.length === 0
? () => testProxyZone.run(testBody, null)
: done => testProxyZone.run(testBody, null, [done]);
```
// jest patch
```
return function(...args) {
return testProxyZone.run(testBody, null, args);
};
```
the purpose of this change is to handle the following cases.
```
test.each([1, 2])('test.each', (arg1, arg2) => {
expect(arg1).toBe(1);
expect(arg2).toBe(2);
});
```
so in jest, it is a little complex, because the `testBody`'s parameter may be bigger than 1, so the
logic in `jasmine`
```
return testBody.length === 0
? () => testProxyZone.run(testBody, null)
: done => testProxyZone.run(testBody, null, [done]);
```
will not work for `test.each` in jest.
So in this PR, I created a dynamic `Function` to return the correct length of paramters (which is required by jest core), to handle
1. normal `test` with or without `done`.
2. each with parameters with or without done.
PR Close #36022
2020-03-11 12:41:19 -04:00
|
|
|
beforeEach(() => {
|
|
|
|
assertInsideProxyZone();
|
|
|
|
});
|
|
|
|
beforeAll(() => {
|
|
|
|
assertInsideProxyZone();
|
|
|
|
});
|
|
|
|
afterEach(() => {
|
|
|
|
assertInsideProxyZone();
|
|
|
|
});
|
|
|
|
afterAll(() => {
|
|
|
|
assertInsideProxyZone();
|
|
|
|
});
|
2020-01-31 10:08:40 -05:00
|
|
|
});
|
|
|
|
describe.each([[1, 2]])('describe.each', (arg1, arg2) => {
|
|
|
|
assertInsideSyncDescribeZone();
|
|
|
|
expect(arg1).toBe(1);
|
|
|
|
expect(arg2).toBe(2);
|
|
|
|
});
|
|
|
|
describe('test', () => {
|
fix(zone.js): zone.js patch jest should handle done correctly (#36022)
`zone.js` supports jest `test.each()` methods, but it
introduces a bug, which is the `done()` function will not be handled correctly.
```
it('should work with done', done => {
// done will be undefined.
});
```
The reason is the logic of monkey patching `test` method is different from `jasmine` patch
// jasmine patch
```
return testBody.length === 0
? () => testProxyZone.run(testBody, null)
: done => testProxyZone.run(testBody, null, [done]);
```
// jest patch
```
return function(...args) {
return testProxyZone.run(testBody, null, args);
};
```
the purpose of this change is to handle the following cases.
```
test.each([1, 2])('test.each', (arg1, arg2) => {
expect(arg1).toBe(1);
expect(arg2).toBe(2);
});
```
so in jest, it is a little complex, because the `testBody`'s parameter may be bigger than 1, so the
logic in `jasmine`
```
return testBody.length === 0
? () => testProxyZone.run(testBody, null)
: done => testProxyZone.run(testBody, null, [done]);
```
will not work for `test.each` in jest.
So in this PR, I created a dynamic `Function` to return the correct length of paramters (which is required by jest core), to handle
1. normal `test` with or without `done`.
2. each with parameters with or without done.
PR Close #36022
2020-03-11 12:41:19 -04:00
|
|
|
it('it', () => {
|
|
|
|
assertInsideProxyZone();
|
|
|
|
});
|
2020-01-31 10:08:40 -05:00
|
|
|
it.each([[1, 2]])('it.each', (arg1, arg2) => {
|
|
|
|
assertInsideProxyZone();
|
|
|
|
expect(arg1).toBe(1);
|
|
|
|
expect(arg2).toBe(2);
|
|
|
|
});
|
fix(zone.js): zone.js patch jest should handle done correctly (#36022)
`zone.js` supports jest `test.each()` methods, but it
introduces a bug, which is the `done()` function will not be handled correctly.
```
it('should work with done', done => {
// done will be undefined.
});
```
The reason is the logic of monkey patching `test` method is different from `jasmine` patch
// jasmine patch
```
return testBody.length === 0
? () => testProxyZone.run(testBody, null)
: done => testProxyZone.run(testBody, null, [done]);
```
// jest patch
```
return function(...args) {
return testProxyZone.run(testBody, null, args);
};
```
the purpose of this change is to handle the following cases.
```
test.each([1, 2])('test.each', (arg1, arg2) => {
expect(arg1).toBe(1);
expect(arg2).toBe(2);
});
```
so in jest, it is a little complex, because the `testBody`'s parameter may be bigger than 1, so the
logic in `jasmine`
```
return testBody.length === 0
? () => testProxyZone.run(testBody, null)
: done => testProxyZone.run(testBody, null, [done]);
```
will not work for `test.each` in jest.
So in this PR, I created a dynamic `Function` to return the correct length of paramters (which is required by jest core), to handle
1. normal `test` with or without `done`.
2. each with parameters with or without done.
PR Close #36022
2020-03-11 12:41:19 -04:00
|
|
|
test('test', () => {
|
|
|
|
assertInsideProxyZone();
|
|
|
|
});
|
|
|
|
test.each([[]])('test.each', () => {
|
|
|
|
assertInsideProxyZone();
|
|
|
|
});
|
|
|
|
});
|
|
|
|
|
|
|
|
it('it', () => {
|
|
|
|
assertInsideProxyZone();
|
|
|
|
});
|
|
|
|
it('it with done', done => {
|
|
|
|
assertInsideProxyZone();
|
|
|
|
done();
|
2020-01-31 10:08:40 -05:00
|
|
|
});
|
|
|
|
|
fix(zone.js): zone.js patch jest should handle done correctly (#36022)
`zone.js` supports jest `test.each()` methods, but it
introduces a bug, which is the `done()` function will not be handled correctly.
```
it('should work with done', done => {
// done will be undefined.
});
```
The reason is the logic of monkey patching `test` method is different from `jasmine` patch
// jasmine patch
```
return testBody.length === 0
? () => testProxyZone.run(testBody, null)
: done => testProxyZone.run(testBody, null, [done]);
```
// jest patch
```
return function(...args) {
return testProxyZone.run(testBody, null, args);
};
```
the purpose of this change is to handle the following cases.
```
test.each([1, 2])('test.each', (arg1, arg2) => {
expect(arg1).toBe(1);
expect(arg2).toBe(2);
});
```
so in jest, it is a little complex, because the `testBody`'s parameter may be bigger than 1, so the
logic in `jasmine`
```
return testBody.length === 0
? () => testProxyZone.run(testBody, null)
: done => testProxyZone.run(testBody, null, [done]);
```
will not work for `test.each` in jest.
So in this PR, I created a dynamic `Function` to return the correct length of paramters (which is required by jest core), to handle
1. normal `test` with or without `done`.
2. each with parameters with or without done.
PR Close #36022
2020-03-11 12:41:19 -04:00
|
|
|
it.each([[1, 2]])('it.each', (arg1, arg2, done) => {
|
2020-01-31 10:08:40 -05:00
|
|
|
assertInsideProxyZone();
|
|
|
|
expect(arg1).toBe(1);
|
|
|
|
expect(arg2).toBe(2);
|
fix(zone.js): zone.js patch jest should handle done correctly (#36022)
`zone.js` supports jest `test.each()` methods, but it
introduces a bug, which is the `done()` function will not be handled correctly.
```
it('should work with done', done => {
// done will be undefined.
});
```
The reason is the logic of monkey patching `test` method is different from `jasmine` patch
// jasmine patch
```
return testBody.length === 0
? () => testProxyZone.run(testBody, null)
: done => testProxyZone.run(testBody, null, [done]);
```
// jest patch
```
return function(...args) {
return testProxyZone.run(testBody, null, args);
};
```
the purpose of this change is to handle the following cases.
```
test.each([1, 2])('test.each', (arg1, arg2) => {
expect(arg1).toBe(1);
expect(arg2).toBe(2);
});
```
so in jest, it is a little complex, because the `testBody`'s parameter may be bigger than 1, so the
logic in `jasmine`
```
return testBody.length === 0
? () => testProxyZone.run(testBody, null)
: done => testProxyZone.run(testBody, null, [done]);
```
will not work for `test.each` in jest.
So in this PR, I created a dynamic `Function` to return the correct length of paramters (which is required by jest core), to handle
1. normal `test` with or without `done`.
2. each with parameters with or without done.
PR Close #36022
2020-03-11 12:41:19 -04:00
|
|
|
done();
|
|
|
|
});
|
|
|
|
|
|
|
|
it.each([2])('it.each with 1D array', arg1 => {
|
|
|
|
assertInsideProxyZone();
|
|
|
|
expect(arg1).toBe(2);
|
|
|
|
});
|
|
|
|
|
|
|
|
it.each([2])('it.each with 1D array and done', (arg1, done) => {
|
|
|
|
assertInsideProxyZone();
|
|
|
|
expect(arg1).toBe(2);
|
|
|
|
done();
|
|
|
|
});
|
|
|
|
|
|
|
|
it.each`
|
|
|
|
foo | bar
|
|
|
|
${1} | ${2}
|
|
|
|
`('it.each should work with table as a tagged template literal', ({foo, bar}) => {
|
|
|
|
expect(foo).toBe(1);
|
|
|
|
expect(bar).toBe(2);
|
|
|
|
});
|
|
|
|
|
|
|
|
it.each`
|
|
|
|
foo | bar
|
|
|
|
${1} | ${2}
|
|
|
|
`('it.each should work with table as a tagged template literal with done', ({foo, bar}, done) => {
|
|
|
|
expect(foo).toBe(1);
|
|
|
|
expect(bar).toBe(2);
|
|
|
|
done();
|
|
|
|
});
|
|
|
|
|
|
|
|
it.each`
|
|
|
|
foo | bar
|
|
|
|
${1} | ${2}
|
|
|
|
`('(async) it.each should work with table as a tagged template literal', async ({foo, bar}) => {
|
|
|
|
expect(foo).toBe(1);
|
|
|
|
expect(bar).toBe(2);
|
|
|
|
});
|
|
|
|
|
|
|
|
test('test', () => {
|
|
|
|
assertInsideProxyZone();
|
|
|
|
});
|
|
|
|
test.each([[]])('test.each', () => {
|
|
|
|
assertInsideProxyZone();
|
2020-01-31 10:08:40 -05:00
|
|
|
});
|
|
|
|
|
|
|
|
test.todo('todo');
|