All geek questions in one place

What to do with non-progressive tests?

Not really a Ruby on Rails issue, but this is the structure we work in.

We transfer data from the old system to our own system and test the code that will perform the data migration. These tests live with the rest of the application tests and therefore work against our build server on commits, etc.

Once we have transferred this data, these tests are likely to be useless for us, because the code they are testing will never be run again. Moreover, the tests are likely to be outdated and may require maintenance so that they do not break our assembly.

Should we just throw away these tests after that? Mark them in some way so that they don’t run after we have done something for real? Something else?

+3
source share
2 answers

Get rid of them. *

* That is, let them sit in the original control, if you ever need to reference them.

+3
source

If it were me, I would single out a project that transfers data along with its tests. Thus, the tests do not generate noise in your current build process, and you only need to change them if you (for some reason) touch the migration project again.

If this is not possible, just take it all away as soon as you're done. If you ever need to return it, it must be in source control mode ... right!?!

+2
source

Source: https://habr.com/ru/post/1754501/

More articles:


All Articles