UNPKG

testeranto

Version:

the AI powered BDD test framework for typescript projects

github.com/adamwong246/testeranto

86 lines (62 loc) • 3.5 kB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
# Testeranto src ## imports External packages are imported first, then local files. Sort these local import statements by "distance" from the current file. ## runtimes there are 3 runtimes- web, node and pure. They all produce a file `exit.log` which describes the final output, or error of a test. This file will capture all uncaught errors. If the last line in this file is '0', the test has passed. If the last line in this file is a number N greater then zero, the test has run to completion, but failed N times. If the last line in this file is a number N less then zero, the test has run errored with code N. ### web - runs via node spawn on v8. - for test subjects which use native packages. (fs, crypto) - automatically produces creates logs: -- exit.log -- stdout.log -- stderr.log ### browser - runs via chrome via puppeteer. - for test subjects which use client globals (window, document) - automatically produces creates logs: -- exit.log -- error.log -- warn.log -- info.log -- debug.log ### pure - runs in the main process via dynamic import - for test subjects which use no platform specific features. - it does not have access to IO, and thus produces no logs automatically. A warning will be shown during the bundle process and calls to console.log will spew into main thread. - automatically produces creates logs: -- exit.log ## metafile The metafile is extra data emitted by the bundling process. Through it, the src files of a test can be ascertained. There is 1 metafile for each of the runtimes. Each is emitted into testeranto/metafiles/runtime/:project.json ## features reporter The report app is capable of showing the features and documentation "collated" into a single place. This is a feature of the React app and has its own route. The `FeaturesReporter` component gathers all the features from all `tests.json` files across all projects, along with the status of individual tests and larger jobs. Maintaining the original file structures, it displays all these features and statuses in a single view, providing a comprehensive overview of the testing landscape. This view takes the list of tests and using the file structures, shows each test as an entry in a tree matching the source code directories. ## Unified Test Editor The test editor combines file navigation, code editing, and test visualization in a single unified interface: - **Three-panel layout**: 1. File Navigator - Project directory structure with test files 2. Code Editor - Monaco-based editor for viewing/editing files 3. Preview Panel - Context-aware visualization: - For `tests.json`: Interactive test results GUI - For other files: Raw content display Key features: - Single interface for both test results and test development - Monaco editor integration for all file types - Preserved test visualization capabilities - Unified file navigation experience - Automatic preview switching based on file type ## Core Testing Principles 1. Tests follow BDD structure with Given/When/Then 2. All tests are strongly typed using I/O/M types 3. Test files are organized in a consistent structure: /src TEST_SUBJECT.ts TEST_SUBJECT.test/ implementation.ts - Concrete test operations specification.ts - Test scenarios and assertions adapter.ts - Test lifecycle hooks types.ts - Type definitions index.ts - Main test export 4. If the test subject is an abstract class, implement this simplest possible mock, and test that mock.