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.

To have a 100% test coverage on ipycytoscape

See original GitHub issue

From @ianhi comment’s:

Still needed:

json graph creation
df graph creation
tests for CytoscapeWidget methods
Tests of adding interaction callbacks
- will require using the mocked comms to fake a message.
typescript tests (need to expand on this and be more specific, please feel free to contribute to this issue with test ideas!)
- maybe use karma-typescript (I think it came with the js cookie cutter)

If you’re adding one of these tests please reference this issue.

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:12 (5 by maintainers)

Top GitHub Comments

2reactions

sven5scommented, Nov 25, 2020

Dataframe graph creation - Create a graph from a pandas dataframe

1reaction

ianhicommented, Jul 22, 2020

will require using the mocked comms to fake a message.

This was just to note that these mocks already exist from the cookiecutter.

maybe use karma-typescript (I think it came with the js cookie cutter)

These have been updated a bit since ipycytoscape was created in order to get them pass. Should be based on the content here: https://github.com/jupyter-widgets/widget-ts-cookiecutter/tree/master/{{cookiecutter.github_project_name}}/tests

Top Results From Across the Web

100% test coverage: Why or why not? - Roelof Jan Elsinga

100 % test coverage simply means you've written a sufficient amount of tests to cover every line of code in your application. That's...

The real benefit of 100% code coverage | by Adrien Guéret

It is better to have 50% of the project tested correctly, than 100% poorly tested. This is correct. It's useless, even counter-productive, to ......

Unit testing code coverage - do you have 100% coverage?

No for several reasons : It is really expensive to reach the 100% coverage, compared to the 90% or 95% for a benefit...

The myth of 100% code coverage - Functionize

For many people, 100% coverage is the mythical ideal that they all strive to achieve. After all, if 100% of your code is...

How 100% Code Coverage Is Destroying Applications

Increasing code coverage to 100% is also detrimental to development cycles. To avoid falling into this trap, all developers should have unit testing...