Should not magic numbers apply to Linter's testing?

So I'm just starting to use a Linter, and I like the No Magic Number rule in general. Unit test files will throw 1000 alerts. This is how they look like:

it (& # 39; getWeekNumber & # 39 ;, function () {
Expect (getWeekNumber (1538918924615)). to.deep.equal ([40, 2018])
expect (getWeekNumber (1536918924615)). to.deep.equal ([37, 2018])
expect (getWeekNumber (1528918924615)). to.deep.equal ([24, 2018])
Expect (getWeekNumber (1438918924615)). to.deep.equal ([32, 2015])
})

There is no real logic here, every programmer can read what is going on in this test case. To change so in my opinion brings no value:

Let someRandomTime1 = 1538918924615
be week40 = 40
let year2018 = 2018
expect (getWeekNumber (someRandomTime1)). to.deep.equal ([week40, year2018])

Here is another example:

it (& # 39; timePadding & # 39 ;, function () {
expect (timePadding (1)). to.equal (& # 39; 01 & # 39;)
expect (timePadding (5)). to.qual (& # 39; 05 & # 39;)
expect (timePadding (19)). to.equal (& # 39; 19 & # 39;
expect (timePadding (111)). to.qual (& # 39; 111 & # 39;)
})

While this program can be clearly programmatically tested, it is simple, readable, and does the job.

Should I not completely disable Linter's magic numbers in component test files?