search

kaustubhhiware / c0derunR

An attempt at a cleaner UI for online IDE's: http://c0derunr.herokuapp.com
MIT License
21 stars 8 forks source link

Adding unittests for the app #18

Open Demfier opened 6 years ago

Demfier commented 6 years ago

It would be really nice if we can add have testing framework. For reference on testing framework for a django app, refer to the django-testing-docs.

kurianbenoy commented 6 years ago

@Demfier I was eager to work on this issue, what kind of test do you want?

kurianbenoy commented 6 years ago

I specifically meant it's all in order and working now, what do we want more to add Tests

To my best of knowledge, test is while developing in django and during application development only.So why do we need test otherwise? Please share your thoughts at @Demfier

Demfier commented 6 years ago

@kurianbenoy - Glad to have someone interested in this issue :smile:

Tests are crucial for any application. Whenever we add new code or modify an existing piece of code, how do you ensure that it is working as expected? For small changes, you can quickly run the app and check its behavior. But when the change is a substantial one (say you upgrade the entire application which can lead to deprecations and a lot of dead code), you can't simply run the app and check each and every unit of the app. You need to automate this stuff (we are in the 21st century for god's sake!) and hence, you write tests for them. Testing isn't just restricted to the development stage, it backs the software even after deployment.

Apart from the reason stated above, some other benefits of writing tests:

  1. You can deal with issues like backward-compatibility when you uptick your apps
  2. You get to use automated cloud testing pipelines like the various CIs available (I really like this one :heart:)

Hope I was able to tell you the importance of tests. You can use the docs link as mentioned in the very first description in case you still feel motivated to take up this task. Let me know if you have any other query.

kurianbenoy commented 6 years ago

@Demfier - thank You for mentioning other uses of Tests 😃

I understood the 1st issue ie to test the problems like backward compatibily you mentioned (As like in case of shifting to Django 2.0 version most of things will show deprecation warnings )

I couldn't understand 2nd point

I will do a bit more research on Tests , (I used tests during development,ie all the experience I have 👐 ) I will inform you specifically before hopping into codebase

kurianbenoy commented 6 years ago

@Demfier I have added a module coverage to check the percent of tests in our repositary

Also I would like a clarification , whether this issue only applicable for unit test in module?

Demfier commented 6 years ago

@kurianbenoy - What do you mean by module in 'this issue applicable only to unit test this module'?

What I initially meant was to have tests written to test every feature we can in the app, like proper complilation of the code, change of template after switching to a different language, proper keyword filtering etc.

On Dec 21, 2017 7:02 AM, "Kurian Benoy" notifications@github.com wrote:

@Demfier https://github.com/demfier I have added a module coverage to check the percent of tests in our repositary

Also I would like to clarify , is this issue only applicable for unit test in module

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/kaustubhhiware/c0derunR/issues/18#issuecomment-353232263, or mute the thread https://github.com/notifications/unsubscribe-auth/AMAyBtmVmGdcSpgP1orE5psRYBin8CAoks5tCbUTgaJpZM4Qo6yv .