VirtualTam's bookmarks
16 bookmarks found
Page 1 of 1
-
- nsnam/ns-3-dev
- Tutorial
- Installation
- Models
- NetAnim - Animates a previously executed simulation using an XML trace file generated during a simulation
-
- https://schema.org/docs/schemas.html
- https://stackoverflow.com/questions/57371445/schema-org-markup-in-emails
- https://softwareengineering.stackexchange.com/questions/328567/how-does-microdata-rdfa-compare-to-json-ld/328711#328711
- https://json-ld.org/
- https://developer.mozilla.org/en-US/docs/Web/HTML/Microdata
- https://developers.google.com/gmail/markup/overview
- https://developers.google.com/gmail/markup/reference/formats/json-ld
- https://developers.google.com/gmail/markup/reference/formats/microdata
- https://docs.microsoft.com/en-gb/outlook/actionable-messages/adaptive-card
-
Packages using struct field tags:
- https://golang.org/pkg/encoding/json/
- https://golang.org/pkg/encoding/xml/
- https://golang.org/pkg/reflect/
- https://github.com/golang/go/wiki/Well-known-struct-tags
Articles:
- https://blog.golang.org/json-and-go
- https://www.golang-book.com/books/intro/9#section1
- https://sosedoff.com/2016/07/16/golang-struct-tags.html
- https://gobyexample.com/json
Threads:
-
RFC 4287 - The Atom Syndication Format
2017-08-09 -
Python unit testing frameworks: Nose, Pytest
2015-02-13 Python's built-in unittest module is quite cool, but a bit limited and way too verbose (read: it's quite not easy to incite developers to write unit tests)
I'm currently looking for more dev-friendly solutions, the key points being:
- writing test code should be easy and straight-forward -keep the focus on "what to test" instead of "how to transcribe a process to a test"
- parallelization! -we, spoiled developers, should make good use of our way-too-many-cores build machines...
- complete feature set!
- we don't want to just run tests...
- coverage reports (find dead/weak/untested code sections)
- output formatting (JUnit-XML seems to be quite a common format out there)
There seem to be 3 solutions in Python:
- stock unittest + project-dependent customizations / test helpers
- nosetests
- py.test
And 2 ways of gettings things done:
- keeping things stock: no external dependency, project-specific implementation...
- using a test framework: one more module in your (test) virtualenv, more concise tests, more features (// run, code coverage, etc.)
Some links:
-
nose: python testing helper
2015-01-04 Includes support for Coverage, Xunit and other cool stuff ;-) Oh, and there is parallel testing, too \o/
nosetests --with-coverage --cover-erase --cover-tests --cover-html --cover-html-dir=htmlcov --with-xunit --xunit-file=unit.xml
via http://www.alexconrad.org/2011/10/jenkins-and-python.html
-
DevDocs — API Documentation Browser
2014-01-22
Page 1 of 1