testeranto 0.143.0 → 0.146.1

package/.aider.input.history

@@ -1330,3 +1330,108 @@
 
 # 2025-07-15 14:07:23.788565
 +n
+
+# 2025-07-15 17:30:57.825360
++/add README.md 
+
+# 2025-07-15 17:31:13.423287
++check README.md for gramatical errors and mispellings 
+
+# 2025-07-15 17:32:58.684258
++make those changes 
+
+# 2025-07-15 17:35:35.565399
++y
+
+# 2025-07-15 17:35:38.026324
++d
+
+# 2025-07-15 17:35:39.509126
++n
+
+# 2025-07-15 17:35:48.802666
++make those changes directly in the readme 
+
+# 2025-07-15 17:49:04.623486
++Make the changes to README. Don
+
+# 2025-07-15 17:49:14.010060
++Make the changes to README. Don't save as blocks- edit README
+
+# 2025-07-15 17:51:12.324771
++n
+
+# 2025-07-15 17:52:28.829475
++lets try again. Edit README.md by fixing any gramatical or spelling errors.
+
+# 2025-07-15 17:53:34.081803
++n
+
+# 2025-07-15 17:55:12.783162
++ok. one more time. I want you to edit README.md, fixing gramatical errors. Don't try to execute it- it is not code, even though it has code samples.
+
+# 2025-07-15 18:00:10.073272
++can you look at README.md and confirm if your changes have been made?
+
+# 2025-07-15 18:00:36.545410
++n
+
+# 2025-07-15 18:00:51.241339
++/add README.md
+
+# 2025-07-15 18:01:16.166071
++/add README.md 
+
+# 2025-07-15 18:01:33.441839
++find and fix any grammatical or spelling mistakes
+
+# 2025-07-15 18:05:09.746853
++https://raw.githubusercontent.com/Prinzhorn/skrollr/refs/heads/master/src/skrollr.js
+
+# 2025-07-15 18:05:11.985806
++y
+
+# 2025-07-15 18:05:14.241580
++n
+
+# 2025-07-15 18:06:25.115070
++/add scripts/compile-docs.js 
+
+# 2025-07-15 18:06:30.692038
++/read index.html 
+
+# 2025-07-15 18:06:44.332376
++/add style.css
+
+# 2025-07-15 18:08:34.262594
++1) Understand that index.html is a generated file. don't edit it directly. Make the change in scripts/compile-docs.js 2) I want you to use skrollr to create a parallax effect. Make a very simple imnplementation first and then I will give you more details 
+
+# 2025-07-15 18:09:28.272256
++y
+
+# 2025-07-15 18:09:28.279182
++/run node scripts/compile-docs.js
+
+# 2025-07-15 18:09:28.279392
++/run node scripts/compile-docs.js
+
+# 2025-07-15 18:09:36.807723
++y
+
+# 2025-07-15 18:15:39.388229
++can you make the parallax effect more pronounced?
+
+# 2025-07-15 18:16:42.881158
++n
+
+# 2025-07-15 18:28:52.392618
++/read docs/style.md
+
+# 2025-07-15 18:29:58.959766
++I have stubbed out an implementation of skrollr in compile-docs on the body tag. I want you to update these gradients 1) With our color pallete 2) a gentle parallax effect so the the background moves slower thant the foreground
+
+# 2025-07-15 18:31:30.828935
++n
+
+# 2025-07-15 18:35:52.490100
++you need to edit compile-docs. You must directly interpolate our official color. Use string values, not css vars. css vars are not available in this context 

package/README.md

@@ -2,24 +2,24 @@
 
 ## The AI-powered BDD test framework for TypeScript projects
 
-#### 🚧 WARNING: Testeranto is still under development and is not ready for production yet. 🚧
+#### 🚧 WARNING: Testeranto is still under development but is not ready for production yet. I am rapidly working to release a beta ASAP. If you are interested in joining this beta program, please context me. 🚧
 
-- README: [index.html](https://adamwong246.github.io/testeranto/)
+- README: [adamwong246.github.io/testeranto/testeranto](https://adamwong246.github.io/testeranto/testeranto)
 - demo: [youtube](https://www.youtube.com/embed/WvU5xMqGi6Q)
 - source: [github.com/adamwong246/testeranto](https://github.com/adamwong246/testeranto)
 - npm: [npmjs.com/package/testeranto](https://www.npmjs.com/package/testeranto)
-- dev: [github.dev/adamwong246/testeranto](https://github.dev/adamwong246/testeranto)
 - example repo: [testeranto-starter](https://github.com/adamwong246/testeranto-starter)
+- tests report: [adamwong246.github.io/testeranto/testeranto](https://adamwong246.github.io/testeranto/testeranto/index.html)
 
 ## What is testeranto?
 
-- Testeranto produces test results which can be fed to Aider.ai to automatically fix failing tests.
-- Testeranto tests are specified in a strongly-typed gherkin-like syntax. Rather than testing your code directly, Testeranto requires you wrap your code with a semantic interface which is based on TS type signatures.
-- Testeranto can run tests in the frontend or the backend, or both.
+- Testeranto produces test results that can be fed to Aider.ai to automatically fix failing tests.
+- Testeranto tests are specified in a strongly-typed gherkin-like syntax. Rather than testing your code directly, Testeranto requires you to wrap your code with a semantic interface that is based on TS type signatures.
+- Testeranto can run tests in the frontend, the backend, or both.
 - Testeranto can be used to test anything that can be bundled with esbuild.
 - Testeranto connects "features" to "tests". This allows the AI to read feature documentation from external systems, like Jira.
-- Testeranto generates test results into static a website which can be deployed to github pages easily.
-- Testeranto uses esbuild to bundle it's tests. The result is used to refine the list of files added to the context of the AI. **The consequence of this is that you can fit all relevant files, and ONLY the relevant files, into the LLMs context.**
+- Testeranto generates test results as a static website that can be easily deployed to GitHub Pages.
+- Testeranto uses esbuild to bundle its tests. The result is used to refine the list of files added to the AI's context. **The consequence of this is that you can fit all relevant files, and only the relevant files, into the LLM's context.**
 
 ## Key Technologies
 
@@ -32,7 +32,6 @@
 | Aider.ai   | AI-powered test fixing                 |
 | ESLint     | Static analysis of test files          |
 | tsc        | Type checking of test files            |
-| Markdown   | Feature documentation format           |
 
 ## Quick Start
 
@@ -80,11 +79,11 @@ yarn t-build rectangle.test.ts yourProject once && yarn t-run rectangle.test.ts
 
 ## Runtime Platforms
 
-|          | Runs on                       | You should use this runtime for...                                                                      | Important differences                                                                                       |
-| -------- | ----------------------------- | ------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
-| **Node** | node V8 with fork             | testing backend code, Node APIs (like `fs` and `crypto`), or anything needing filesystem access         | has access to the filesystem and io                                                                         |
-| **Web**  | chrome browser                | testing frontend code, anything that uses `document` or `window`, UI interactions, or visual regression | can take screenshots/recordings                                                                             |
-| **Pure** | node v8, dynamically imported | testing code which can run on both node-v8 and the the browser                                          | Very similar to "Node" but has no IO access and thus, no console.log. This runtime is theoretically faster. |
+|                                          | You should use this runtime for...                                                                      | Important differences                                                                                      |
+| ---------------------------------------- | ------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
+| **Node** : node V8 with fork             | testing backend code, Node APIs (like `fs` and `crypto`), or anything needing filesystem access         | has access to the filesystem and io                                                                        |
+| **Web** : chrome browser                 | testing frontend code, anything that uses `document` or `window`, UI interactions, or visual regression | can take screenshots/recordings                                                                            |
+| **Pure** : node v8, dynamically imported | testing code that can run on both node-v8 and the browser                                               | Very similar to "Node" but has no IO access and thus no console.log. This runtime is theoretically faster. |
 
 ## CLI Commands
 
@@ -123,7 +122,7 @@ yarn t-aider
 Testeranto generates a "prompt" alongside test results. This prompt is passed to aider as input.
 
 ```
-// input src files which can be edited by aider
+// input src files that can be edited by Aider
 /add test/node.ts
 
 // test report files that inform aider but should not be edited
@@ -161,29 +160,29 @@ test0: Given.Default(
 
 ```
 
-## Sidecars (COMING SOON)
+## `eslint` and `tsc`
 
-Along side your test, you can include a number of "sidecars" which are other bundled javascript assets upon which your test depends. For example, suppose you have an app with a frontend and backend component. You could run a react test in the web and include the node http server as a sidecar.
+Alongside the BDD tests, Testeranto runs ESLint and tsc on the input files to generate a list of static analysis errors and type errors, respectively.
 
-## `eslint` and `tsc`
+## Sidecars (COMING SOON)
 
-Alongside the bdd tests, testeranto runs eslint and tsc upon the input files to generate a list of static analysis errors and a list of type errors, respectively.
+Alongside your test, you can include a number of "sidecars" - other bundled JavaScript assets upon which your test depends. For example, suppose you have an app with frontend and backend components. You could run a React test in the web and include the Node HTTP server as a sidecar.
 
 ## Subprojects
 
-Testeranto has a core repo, but there are also subprojects which implement tests by type and by technology
+Testeranto has a core repo, but there are also sub-projects which implement tests by type and by technology
 
 ### testeranto-solidity
 
-Test a solidity contract. Also included is an example of deploying a contrct to a ganache server.
+Test a solidity contract. Also included is an example of deploying a contract to a ganache server.
 
 ### testeranto-reduxtoolkit
 
-Test a redux store.
+Tests a Redux store.
 
 ### testeranto-http
 
-Test a node http server.
+Tests a Node HTTP server.
 
 ### testeranto-react (COMING SOON)