question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Increase code coverage across different modules (easy ones)

See original GitHub issue

🐞 Problem The goal is 100% code coverage. It’s not a very realistic goal because sometimes we lack the knowledge to do so. But I am listing some of the parts, where coverage can be increased easily.

🎯 Goal

Try to target these files. The lines untested would be marked red here.

  • coordinates/core.py (#394)
  • ijit.py (#397)
  • symbolic/vector.py
  • symbolic/tensor.py
  • plotting/hypersurface/core.py
  • plotting/rays/shadow.py
  • rays/shadow.py

💡 Possible solutions

  • What is coverage
  • tests are present in src\einsteinpy\tests\test_<module name>\test_<file name>

📋 Steps to solve the problem

  • Comment below about what you’ve started working on.
  • Add, commit, push your changes
  • Submit a pull request and add this in comments - Addresses #<put issue number here>
  • Ask for a review in comments section of pull request
  • Celebrate your contribution to this project 🎉

@shreyasbapat if possible, add some more!

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:3
  • Comments:9 (8 by maintainers)

github_iconTop GitHub Comments

1reaction
ritzvikcommented, Jan 24, 2020

Hey i’m still taking a bit too much time on it , im currently creating tests for coordinates/core if anyone wants to work on the other files please go ahead.

Open a PR with whatever you have, we’ll refine it over there.

Also @shreyasbapat and @ritzvik i fail to find a test module for coordinates/core file should i make one or insert my tests in an existing test module for coordinates. Thanks again.

Put them in test_coordinates/tests_coord_transform.py.

1reaction
Bhavamcommented, Jan 20, 2020

Working on this , will create PR soon.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Improve Code Quality Using Test Coverage - CODE Magazine
In this article, I'll introduce the concept of code coverage by exploring the value of measurements such as statement coverage, function ...
Read more >
Improve your component test coverage with this one weird trick
For this project, we used three such tools to improve code quality: Facebook's Flow type checker, Eslint and SonarQube. Keep this in mind, ......
Read more >
Increase your code coverage using Istanbul | by Abha Gupta
The best way to get 100% coverage is to keep evaluating coverage as you develop the code.
Read more >
How to fix a drop of code coverage with a multi module Maven ...
A good practice is to add the plugin with all the executions to your parent pom in the pluginManagement section. Now, when maven...
Read more >
What is best practice for generating multiple code coverage ...
IMHO, you should map your teams to existing modules or refactor your code in order to make sure that a module is only...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found