Is it too late to cover with tests (Rspec) a project that has been implemented for a long time?

E

eldar_web2017-10-24 19:43:11

Software testing

eldar_web, 2017-10-24 19:43:11

There is a Ruby on Rails project that has been running for a long time.
Just started learning testing on Rspec and using.
Does it make sense to write tests for an already existing project, or is it better not to write them?

Reply

Answer the question

In order to leave comments, you need to log in

2 answer(s)

R

Roman Mirilaczvili, 2017-10-24
@eldar_web

It's late, but it's better to have some tests than not to have any at all.
You can cover key places with tests and expand tests as needed.

S

Sergey Krasnodemsky, 2018-07-19
@Prognosticator

Cover.
How to make changes, architectural in particular, if there is no certainty that the code will continue to work?
How to make code testable?
Write tests.
Tests are also documentation.
And tests are just part of the flow.
What to cover - everything is important in an application. Policy, authentication, services, requests to api, if the UI is established, then it.