What is the Neural Link?

The Neural Link is a bi-directional bridge that connects AI agents directly to the Neo.mjs runtime. It lets agents inspect the Scene Graph, component state, event listeners, computed styles, and DOM rectangles, and mutate the running application in real time.

Why is Neo.mjs called an Application Engine instead of a framework?

Neo.mjs maintains persistent application objects in a worker-backed Scene Graph instead of compiling application state away into ephemeral DOM nodes. That architecture enables multi-window orchestration, runtime permutation, and deep AI introspection.

What is Context Engineering?

Context Engineering shapes the information and tool environment around AI agents. Neo.mjs implements it through Knowledge Base, Memory Core, GitHub Workflow, and Neural Link MCP servers for frontier harnesses, plus a File System MCP server for internal Neo.ai.Agent local loops.

What is the Neo.mjs Agent OS?

The Neo.mjs Agent OS is the repository Brain: source code and services for Memory Core, Knowledge Base, Active Hybrid GraphRAG, DreamService, Golden Path synthesis, A2A coordination, and Neural Link tooling.

Frontmatter

id	6001
title	Hacktoberfest: Creating more component tests
state	Closed
labels	enhancementhelp wantedgood first issuehacktoberfest
assignees	[]
createdAt	Oct 2, 2024, 1:05 AM
updatedAt	Nov 2, 2024, 2:00 PM
githubUrl	https://github.com/neomjs/neo/issues/6001
author	tobiu
commentsCount	1
parentIssue	5963
subIssues	6029 Component Tests: Button
subIssuesCompleted	1
subIssuesTotal	1
blockedBy	[]
blocking	[]
closedAt	Nov 2, 2024, 2:00 PM

Hacktoberfest: Creating more component tests

Closed v8.0.0-alpha.1/archive-v8-0-0-alpha-1-chunk-1 enhancementhelp wantedgood first issuehacktoberfest

tobiu commented on Oct 2, 2024, 1:05 AM

Related to the Hacktoberfest Welcome ticket: https://github.com/neomjs/neo/issues/5963 (Please read this ticket first)

This is a shout-out to all automated Testers out there.

We already started to write unit tests for the vdom engine, collections and the custom class config system: https://github.com/neomjs/neo/tree/dev/test/siesta/tests

We also created a couple of component tests using Siesta 5: https://github.com/neomjs/neo/tree/dev/test/components

Nick @canonic-epicure, the creator of the Siesta Testing Tool, did create a PoC for Siesta 6: https://github.com/neomjs/neo/tree/siesta6/test/siesta6 (all unit tests work)

Siesta v6 is a super nice project which is using PlayWright to generate headless browsers: https://github.com/bryntum/siesta

The PoC for component based testing in v6 is still missing (we might need Nicks help on this one).

Inside the hacktoberfest scope, this would be worth a lot of PRs => at least one for each component (also, one for basic testing of one component and additional PRs for more advanced tests). As a follow-up, we could also automatically test examples & demo apps.

Please let me know, in case anyone is interested in writing more tests, especially for the component library. This would help us a lot with avoiding future regression bugs.

Thanks and best regards, Tobi

tobiu added the help wanted label on Oct 2, 2024, 1:05 AM

tobiu added the good first issue label on Oct 2, 2024, 1:05 AM

tobiu added the hacktoberfest label on Oct 2, 2024, 1:05 AM

tobiu added the enhancement label on Oct 2, 2024, 1:06 AM

tobiu Nov 2, 2024, 2:00 PM

Since the event has ended, i will close all hacktoberfest related tickets now. In case someone still wants to work on a related ticket, feel free to add a comment and we can reopen it.

tobiu closed this issue on Nov 2, 2024, 2:00 PM