Change Details

Currently the e2e tests are (a) tightly coupled to Codex implementation and (b) written similar to unit tests (i.e. testing edge cases), we'd like to simplify and make the tests more robust by defining a "happy path" to test and leveraging simpler selectors for codex components. Happy path: # Create a function # Add an code implementation # Add a tester # Add a composition implementation # Run the function # Enable the function --- [x] basic.js [] **WIP** function.js [] connect.js [] implementation.js [] tester.js [] type.js

Currently the e2e tests are (a) tightly coupled to Codex implementation and (b) written similar to unit tests (i.e. testing edge cases), we'd like to simplify and make the tests more robust by defining a "happy path" to test and leveraging simpler selectors for codex components. Happy path: # Create a function # Add an code implementation # Add a tester # Add a composition implementation # Run the function # Enable the function --- [x] basic.js [x] function.js [ ] connect.js [ ] implementation.js [x] tester.js [ ] type.js

Currently the e2e tests are (a) tightly coupled to Codex implementation and (b) written similar to unit tests (i.e. testing edge cases), we'd like to simplify and make the tests more robust by defining a "happy path" to test and leveraging simpler selectors for codex components. Happy path: # Create a function # Add an code implementation # Add a tester # Add a composition implementation # Run the function # Enable the function --- [x] basic.js [] **WIP**x] function.js [ ] connect.js [ ] implementation.js [x] tester.js [ ] type.js