Implement more test cases on Chisel types to prevent future crashes

[rameloni]

The test/ directory contains tests for the simulators implemented in this repo (ParametricSimulator and TywavesSimulator). Since, covering all the possible designs is quite difficult, these tests help in reducing the chances of unexpected failures while using Tywaves.

The Chisel explanation page contains all available Chisel constructs. This issue asks for implementing test cases using all the constructs available to make Tywaves even more robust.

[rameloni]

Some tests are already implemented covering almost all Chisel features and constructs. Here, is a full list of tasks to implement the missing tests (_the list includes also features already covered in the current version).

• Ground Data Types - tested and working but explicit tests are welcome
• Bundles and Vecs - https://www.chisel-lang.org/docs/explanations/bundles-and-vecs
• Modules
• Memories
• BlackBoxes
• Enumerations
• DataView
• Muxes
• Reset
• Polymorphism and Parameterization
• Print statements
• Decoders
• Intrinsic Modules
• Properties
• Layers
• Some other features are not closely related to Tywaves and their behaviour is covered by other constructs. However, it is a good practice to write tests for them as well.
  • Combinational Circuits
  • Operators
  • Width Inference
  • Functional Abstraction
  • Ports
  • Sequential Circuits
  • Interfaces and Connections
  • Functional Module Creation
  • MultiClocks
  • Connectable operators