What areas of testing to choose before the release? Which are more priority, which are less?

Question

Software testing

In one test task for a tester, I found the following question:
"Which areas of project testing before release will you choose as the highest priority for testing and which are the least priority?"
And I understand that I do not understand what is meant by "testing area". Please tell me how to answer!
I think there are two options:
1. Select the product components to test first or last. But it is not specified what kind of project.
2. Types of testing (smok, regression, load, etc.). In this case, how to answer, in your opinion?
Thank you!

Answer 1

In general, Sergei , of course, may be right. The question is vague enough to not have a correct answer at all.
It seems to me that the question is more about item 2 from your question (types of testing).
In this case, smoke-testing -> regression is the highest priority before the release. they cover the basic requirements for what has already been implemented.
Those. in case of a successful passage of smoke and regression -> you at least make sure that the released functionality did not break the previously implemented one (i.e. did not make it worse).
And then, already, testing the functionality itself.

Answer 2

Smoke testing is always done first. All other test suites come after a successfully passed smoke. For many more or less large projects, smokes are automated and run not only on pre-release builds, but also on all intermediate ones. After a successful smoke test, the main functional test follows, respectively, this is functional testing. Then there are other types of testing. But if you read the question carefully...
"What areas of project testing before release will you choose as the highest priority" - if this was a question at an interview, I would answer that we first perform smoke testing, and then we check those program modules that have changed at the last moment. It is there that bugs can fall out at the release stage. other components have already been tested in several other test cycles and should work fine.

Answer 3

function ololo(obj, count = 1) {
  let values = Object.values(obj)
  if (count === 1)
    return values
  else
    return new Array(count).fill(values)
}

https://jsfiddle.net/hbeb6h02/

Answer 4

Read the materiel, in JS an array is an object.
javascript.ru/tutorial/object/intro