Skip to content

Piero Bosio Social Web Site Personale Logo Fediverso

Social Forum federato con il resto del mondo. Non contano le istanze, contano le persone

Ciao ragazzi

Uncategorized
7 5 3
Feed RSS

Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • Problemi con la bilancia

    Uncategorized
    2
    0 Votes
    2 Posts
    0 Views
    @GustavinoBevilacqua soprattutto se vai a piedi
  • 0 Votes
    1 Posts
    0 Views
    I overslept and missed the eclipse before the fog rolled in in Venice Beach.
  • 0 Votes
    1 Posts
    0 Views
    Non importa chi cazzo sei e quanti soldi vuoi darmi. Se mi tieni in call fino alle 13.00 ti becchi tutto il mio "mi scusi, mi devo assentare un attimo, si sta attaccando il sugo".#Ufficio #CotturaLenta
  • 0 Votes
    1 Posts
    1 Views
    I have a question about Python libraries and testing scope.If I'm importing 'serial' in my library, and use it like the following to create a connection to a sensor:--- start code ---import serialclass Sensor: def __init__(self, serial_device): self.__serial_device = serial_device try: self.__connection = serial.Serial( port=serial_device, baudrate=9600, bytesize=serial.EIGHTBITS, parity=serial.PARITY_NONE, stopbits=serial.STOPBITS_ONE, ) except serial.SerialException: print("Could not establish serial connection to sensor")--- end code ---how much testing should I do around the serial connection? Just mock up a few buffers (byte streams), and see how my class handles unexpected input?One the one hand, I want to make the library as solid as possible. On the other hand, I don't want to run tests on code I don't control (the library module). I know of the 'mock-serial' utility, but haven't used it.The aim is to make a Python version of my Arduino library for the CozIR Ambient CO2 sensor:https://codeberg.org/mjack/ambientCO2/src/branch/develop#python #unittest #testing #sensors