M25 Columbus, OH stats & predictions

[Image Placeholder – Picture depicting trophy awarded victor post-match celebration]

[Image Placeholder – Image capturing exhilarated fans applauding triumphant team returning court after hard-fought win]

[Image Placeholder – Photo showing group friends gathered bar area discussing favorite moments shared live viewing session]

[Image Placeholder – Visual representing diverse audience demographics representing wide range ages interests converging unite passion shared love sport transcending boundaries bringing people together common cause]<|repo_name|>/alldatacenter/alldata<|file_sep|>/_FULLTEXT/cesanta.mjs-unit.md mjs-unit - JavaScript Unit Testing Framework mjs-unit is a simple JavaScript unit testing framework designed specifically for embedded systems development using MicroJS library (http://cesanta.com/microjs). mjs-unit provides basic test runner functionality with minimal overhead (it doesn't require any external libraries) while allowing custom test harnesses implementations via module exports interface provided by MicroJS (http://cesanta.com/microjs/#module_exports). Features * Lightweight framework implementation suitable even for resource-constrained embedded systems * Simple API * Modular architecture allows integration into existing projects * Built-in assertion library * Supports asynchronous tests * Test grouping via modules * Test results logging via custom harnesses API Limitations * No code coverage support See also jsunit project (http://www.jsunit.org/) which implements similar functionality but requires additional JS runtime libraries (such as JScript.NET) or embedding into HTML page using browser JS engine which may not be feasible on some embedded devices or applications running outside browser environment Examples To run tests simply include mjs-unit.js file in your project source tree somewhere after including micro.js file then call runTests() function from your main application code e.g.: // Include required libraries var micro = require('micro'); var mjs_unit = require('mjs_unit'); // Define tests module 'foo' exports.module.exports = { // Run tests after system initialization function init() { mjs_unit.runTests(); } }; // Define foo.test.js file containing actual tests var assert = mjs_unit.assert; module.exports = { // Define test 'test_foo' test_foo : function(test) { assert.equal(1 + '23', '123'); }, }; Note that foo.test.js file must not export anything else except functions prefixed by test_ prefix so that they are automatically picked up by framework during execution You can also use custom test harnesses instead of default console-based one provided by framework e.g.: // Include required libraries var micro = require('micro'); var mjs_unit = require('mjs_unit'); // Define custom harness exports.module.exports = { init : function() {}, // Called once at start-up log : function(msg) {}, // Used internally by framework finalize : function() {} }; // Run tests using our custom harness mjs_unit.runTests({ harness : exports }); See documentation below Custom Harness API Framework allows defining custom test harnesses via module.exports interface provided by MicroJS library Default console-based harness simply outputs test results directly onto console using console.log() method but you can define your own harness implementing following interface methods init() Called once at start-up log(msg) Used internally by framework finalize() Called once after all tests have finished running Usage To use custom harness define it as separate file somewhere in your project source tree e.g.: /myproject/my_custom_harness.js then include it along with other required files e.g.: /myproject/main.cxx #include "micro.h" void main(void) { micro::require("micro"); micro::require("mjs_unit"); micro::require("my_custom_harness"); my_custom_harness.init(); ... } Then pass reference to your custom harness object when calling runTests() function e.g.: my_custom_harness.runTests({ harness : my_custom_harness }); See documentation below License MIT License Copyright (c)2010 Cesanta Software Limited Permission is hereby granted free of charge to any person obtaining copy of this software along with associated documentation files (the "Software") to deal in the Software without restriction including without limitation rights to use copy modify merge publish distribute sublicense and/or sell copies of the Software and permit persons whom Software is furnished to do so subject to following conditions * Above copyright notice this permission notice shall be included in all copies or substantial portions of the Software * Neither name of Cesanta nor names of its contributors may be used endorse or promote products derived from this software without specific prior written permission Documentation Module Exports Interface Custom Harness API Module exports interface allows implementing custom test harnesses within same project space as main application code In addition standard MicroJS module.exports interface exposed via exports variable it also provides access private variables used internally by framework _tests array containing list of all defined tests _current_test currently executing test _test_count number of defined tests _test_index index currently executing test _result current test result object containing passed failed skipped total fields Test Results Logging Functions When implementing custom harnesses you need implement following functions according internal requirements Log Function This function gets called internally by framework whenever new message needs logged log(msg) Parameters msg String containing message describing current status Return Value None Init Function This function gets called once immediately after starting testing process init() Parameters None Return Value None Finalize Function This function gets called once immediately after finishing testing process finalize() Parameters None Return Value None Assertion Library Assertions allow verifying expected behavior during unit testing Tests usually verify correctness expected output given certain input values Assertions are used within each individual unit test Functions provided by assertion library allow comparing expected output against actual one produced by code under test Each assertion produces either PASS FAIL or SKIP result depending on outcome Assert Equal Function assert.equal(actual expected msg) Compares two values asserting they are equal Parameters actual Expected value Actual value being compared msg Optional string message describing current assertion Returns None Throws AssertionError if values don't match Assert Not Equal Function assert.notEqual(actual expected msg) Compares two values asserting they are not equal Parameters actual Expected value Actual value being compared msg Optional string message describing current assertion Returns None Throws AssertionError if values do match Assert True Function assert.true(actual msg) Asserts that given value evaluates true Parameters actual Actual value being checked msg Optional string message describing current assertion Returns None Throws AssertionError if value evaluates false Assert False Function assert.false(actual msg) Asserts that given value evaluates false Parameters actual Actual value being checked msg Optional string message describing current assertion Returns None Throws AssertionError if value evaluates true Assert Null Function assert.null(actual msg) Asserts that given value evaluates null Parameters actual Actual value being checked msg Optional string message describing current assertion Returns None Throws AssertionError if value does not evaluate null Assert Not Null Function assert.notNull(actual msg) Asserts that given value does not evaluate null Parameters actual Actual value being checked msg Optional string message describing current assertion Returns None Throws AssertionError if value evaluates null Async Support Asynchronous Tests Many embedded system applications rely heavily on external resources such as network connections sensors etc which cannot always return immediate results Therefore it may be necessary write asynchronous unit tests capable handling asynchronous operations Asynchronous operations typically involve passing callback functions which get executed once operation completes Asynchronous assertions provide means verifying correctness asynchronous operations Example Below shows example asynchronous unit test verifying correctness HTTP GET request made using hypothetical http.get(url callback response status_code error_msg response_body error_code error_msg parameters url URL being requested callback Callback invoked once request completes status_code HTTP status code returned response Body content returned error_msg Error message returned error_code Error code returned response_body Body content returned error_msg Error message returned asyncTest_http_get : function(test) { http.get('http://www.example.com',function(status_code response_body error_msg){ try { assert.equal(status_code '200 OK'); } catch(e){ throw(e); } try { assert.notEqual(error_code undefined); } catch(e){ throw(e); } try { assert.notEqual(error_msg undefined); } catch(e){ throw(e); } try { assert.notEqual(response_body undefined); } catch(e){ throw(e); } finally{ finishTest(test); } }); }, Async Assertions Async assertions allow verifying correctness asynchronous operations Similar synchronous assertions they provide means comparing expected output against actual one produced asynchronously However unlike synchronous assertions async assertions don't throw errors upon failure Instead they invoke finishTest(test_object) method passed callback parameter indicating whether operation succeeded or failed Example Below shows example usage asyncAssertTrue(async_condition callback_function parameters ...) Invokes callback_function only if async_condition returns true Otherwise skips invocation Params async_condition Callable condition evaluated asynchronously returns true/false callback_function Callback invoked only if async_condition returns true Params ... Variable number arguments passed directly into callback_function Returns None Example Below shows example usage asyncAssertFalse(async_condition callback_function parameters ...) Invokes callback_function only if async_condition returns false Otherwise skips invocation Params async_condition Callable condition evaluated asynchronously returns true/false callback_function Callback invoked only if async_condition returns false Params ... Variable number arguments passed directly into callback_function Returns None Example Below shows example usage finishTest(test_object result [msg]) Finishes currently executing asynchronous unit test Result determines whether operation succeeded failed Msg optional string description reason why operation failed Params result Boolean indicating whether operation succeeded failed Default false Indicates failure Msg optional String description reason why operation failed Defaults none Indicates success Returns None <|repo_name|>/alldatacenter/alldata<|file_sep