Set up comprehensive frontend testing infrastructure
- Install Jest for unit testing with React Testing Library - Install Playwright for end-to-end testing - Configure Jest with proper TypeScript support and module mapping - Create test setup files and utilities for both unit and e2e tests Components: * Jest configuration with coverage thresholds * Playwright configuration with browser automation * Unit tests for LoginForm, AuthContext, and useSocketIO hook * E2E tests for authentication, dashboard, and agents workflows * GitHub Actions workflow for automated testing * Mock data and API utilities for consistent testing * Test documentation with best practices Testing features: - Unit tests with 70% coverage threshold - E2E tests with API mocking and user journey testing - CI/CD integration for automated test runs - Cross-browser testing support with Playwright - Authentication system testing end-to-end 🚀 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
77
frontend/node_modules/makeerror/readme.md
generated
vendored
Normal file
77
frontend/node_modules/makeerror/readme.md
generated
vendored
Normal file
@@ -0,0 +1,77 @@
|
||||
makeerror [](http://travis-ci.org/nshah/nodejs-makeerror)
|
||||
=========
|
||||
|
||||
A library to make errors.
|
||||
|
||||
|
||||
Basics
|
||||
------
|
||||
|
||||
Makes an Error constructor function with the signature below. All arguments are
|
||||
optional, and if the first argument is not a `String`, it will be assumed to be
|
||||
`data`:
|
||||
|
||||
```javascript
|
||||
function(message, data)
|
||||
```
|
||||
|
||||
You'll typically do something like:
|
||||
|
||||
```javascript
|
||||
var makeError = require('makeerror')
|
||||
var UnknownFileTypeError = makeError(
|
||||
'UnknownFileTypeError',
|
||||
'The specified type is not known.'
|
||||
)
|
||||
var er = UnknownFileTypeError()
|
||||
```
|
||||
|
||||
`er` will have a prototype chain that ensures:
|
||||
|
||||
```javascript
|
||||
er instanceof UnknownFileTypeError
|
||||
er instanceof Error
|
||||
```
|
||||
|
||||
|
||||
Templatized Error Messages
|
||||
--------------------------
|
||||
|
||||
There is support for simple string substitutions like:
|
||||
|
||||
```javascript
|
||||
var makeError = require('makeerror')
|
||||
var UnknownFileTypeError = makeError(
|
||||
'UnknownFileTypeError',
|
||||
'The specified type "{type}" is not known.'
|
||||
)
|
||||
var er = UnknownFileTypeError({ type: 'bmp' })
|
||||
```
|
||||
|
||||
Now `er.message` or `er.toString()` will return `'The specified type "bmp" is
|
||||
not known.'`.
|
||||
|
||||
|
||||
Prototype Hierarchies
|
||||
---------------------
|
||||
|
||||
You can create simple hierarchies as well using the `prototype` chain:
|
||||
|
||||
```javascript
|
||||
var makeError = require('makeerror')
|
||||
var ParentError = makeError('ParentError')
|
||||
var ChildError = makeError(
|
||||
'ChildError',
|
||||
'The child error.',
|
||||
{ proto: ParentError() }
|
||||
)
|
||||
var er = ChildError()
|
||||
```
|
||||
|
||||
`er` will have a prototype chain that ensures:
|
||||
|
||||
```javascript
|
||||
er instanceof ChildError
|
||||
er instanceof ParentError
|
||||
er instanceof Error
|
||||
```
|
||||
Reference in New Issue
Block a user