Bring test-coverage up
Target:
-
> 95%
forcqparts
core library -
> 80%
forcqparts_*
parts libraries
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (9 by maintainers)
Top Results From Across the Web
Get free at-home COVID-19 tests this winter
The tests available for order: Are rapid antigen at-home tests, not PCR; Can be taken anywhere; Give results within 30 minutes (no lab...
Read more >Tests - IDRlabs
This page provides an overview of all the free online tests at IDR Labs, including tests in psychology, politics, and more.
Read more >Personality, IQ, career, love, health and attitude tests
Tests & quizzes: free IQ test, Big 5 personality test, emotional intelligence test (EQ), love tests, career aptitudes test, self-esteem self-test, ...
Read more >Self Tests | Psychology Today
Self Tests. Are you outgoing or introverted? Do you have a high traditional IQ or emotional IQ? Do you have what it takes...
Read more >COVID-19 Testing: What You Need to Know - CDC
Testing is not recommended to detect a new infection. My first positive test result was within: 21-90 days. I have symptoms. Use antigen...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Added catalogue test automation, documented here. So you can test an entire library catalogue by witing:
That will be picked up by
python -m unittest discover
, and run 1 test per catalogue entry. To demonstrate, the test directory’spartslib
is tested, resulting in:Each part’s geometry is built, and assembly constraints are solved… ultimately it’s currently just making sure all deviations listed in the catalogue can be generated without an exception being raised.
I’m quite proud of that one 😊 Next step is to create catalogues for existing components, so they may be tested using this method.
Just discovered that the
CatalogueTest
utility was just re-creating the same part over and over again… fixed in 698a0c1. The above catalogue tests were re-run with no issue… phew!