GlaDOS dev-docs
  • Introduction
  • Getting started
    • Pre-requisite
    • Installation
    • Creating our first function
  • Prism's Features
  • Prism Compiler
  • Prism Bytecode File Structure
  • Exeption Handling
  • Grammar language
  • Test Policy
    • Unit & integration tests
    • Continuous Integration and Deployment (CI/CD)
  • Appendix
Powered by GitBook
On this page
  1. Test Policy

Unit & integration tests

Last updated 1 year ago

We utilized the hspec framework and hspec-discovery to perform comprehensive unit testing. By leveraging this powerful combination, we were able to automatically detect and categorize any file ending with "Spec.hs" as a test.

This streamlined approach ensured thorough testing coverage across our project. Since we are utilizing a stack machine architecture, we have taken the initiative to create a tailored set of instructions specifically designed for our system. As a part of this process, we have meticulously crafted a comprehensive range of tests to ensure the robustness and accuracy of our implementation.

Here is a preview of the make tests_run command and the current coverage of our tests: