Jump to content
  • Sky
  • Blueberry
  • Slate
  • Blackcurrant
  • Watermelon
  • Strawberry
  • Orange
  • Banana
  • Apple
  • Emerald
  • Chocolate
  • Charcoal

Search the Community

Showing results for tags 'test suite'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • OpenComputers
    • Announcements
    • Feedback
    • IRC
  • Code Central
    • Support
    • Showcase
    • Tutorials
  • Addons & More
    • Addons Mods
    • Architectures
    • OpenEngineering Task Force
  • General
    • Lounge
    • Forum Games
    • Showcase
    • Servers
  • Archives
    • Public Archives

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL








Fediverse ID



Found 1 result

  1. Twire (Testing Wire) is a small and simple unit testing API made for running automated tests, this is useful if you're in the need of testing every time if your new added features, or the old ones keep going as intended. The repository: https://github.com/sigmasoldi3r/oc-twire You may ask, why a testing suite? The reason behind making a testing suite is because I was tired of making random test.lua files that included few prints to check if all was going OK, so this makes this process much more easy to understand, if something fails and easy to see that everything is going as expected. In fact, I was also motivated by the idea of making in a future test runners like in other programming languages and environments is done. Installation To install the version 1.0.0 which is the current beta release, just paste this code in your shell with the insert key: (Of course you'll need an internet card, and this is intended to run with a tier-3 GPU and screen) Press enter and the library will be installed. If this topic gets outdated any time, you can check the repository (Look at the top) to see if there are new releases, updates or issues solved. If you have any issue or proposal you can post them at the repository issue tracker You're welcome in contributing at any time! Usage In the readme you'll find a simple usage example, I'll give you a brief explanation here: With the function describe you tell what you're doing or about to test, the second argument is the function inside the test. With the function it you describe what it should do, then the second argument (again) is the function that will be tested for failed assertions. Inside 'it', you assert conditions with the assert table of twire, like assert.equal(5, 6); which will result in a failed test because 5 == 6 will never be true (I hope so).
  • Create New...

Important Information

By using this site, you agree to our Terms of Use and Privacy Policy.