scientist.js - GitLite

KO | EN

gitlite — search

#hacktoberfest #react #golang #android #docker #nodejs #windows #awesome #kubernetes #pytorch #security #openai #ios #open-source

scientist.js

(★ 608)

:microscope: A JavaScript interpretation of the Ruby library Scientist, a library for carefully refactoring critical paths.

파일 탐색기

최종 버전 다운로드 (.zip)

- main.js
- model.js
- my-widget.js
- permission.js
- user.js
- - bad-behaviour-error.js
  - behaviour-missing-error.js
  - behaviour-not-unique-error.js
- base-experiment.js
- datetime-provider.js
- experiment.js
- index.js
- observation.js
- random-provider.js
- result-publisher.js
- result.js
- bad-behavior-error.spec.js
- behavior-missing-error.spec.js
- behavior-not-unique-error.spec.js
- date-time-provider.spec.js
- experiment.spec.js
- observation.spec.js
- result.spec.js
.babelrc
.gitignore
.npmignore
.travis.yml
package.json
README.md
UNLICENSE

# 설치 가이드

1. 코드 내려받기

git clone https://github.com/bugthesystem/scientist.js

깃허브에서 프로젝트 코드 전체를 내 컴퓨터로 내려받습니다.

cd scientist.js

방금 내려받은 프로젝트 폴더 안으로 이동합니다.

2. Node.js

쉬움 추천

사전 준비물

Git GitHub에서 프로젝트 코드를 내려받으려면 필요합니다.
Node.js npm 명령어를 쓰려면 Node.js가 설치되어 있어야 합니다. LTS(장기지원) 버전을 추천합니다.

npm install scientist.js

package.json에 명시된 라이브러리들을 내려받아 설치합니다.

✅ 명령어 실행 후 터미널에 나타나는 주소(보통 http://localhost:3000 형태)를 브라우저에서 열어보세요.

이 레포의 README에 적힌 실제 명령어를 그대로 가져왔습니다.

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# scientist.js
:microscope: A JavaScript interpretation of the Ruby library [Scientist](https://github.com/github/scientist), a library for carefully refactoring critical paths.

[![Build Status](https://travis-ci.org/ziyasal/scientist.js.svg?branch=master)](https://travis-ci.org/ziyasal/scientist.js) [![Coverage Status](https://coveralls.io/repos/github/ziyasal/scientist.js/badge.svg?branch=master)](https://coveralls.io/github/ziyasal/scientist.js?branch=master)

**Install**
```sh
npm install scientist.js
```

How do I science?
========================

Let's pretend you're changing the way you handle permissions in a large web app. Tests can help guide your refactoring, but you really want to capture the current and refactored behaviours under load.

**ES6 Sample**
```js
import {Experiment, Result} from 'scientist.js';

import Permission from './permission';
import Model from './model';

class MyWidget {
    constructor() {
        this.model = new Model();
    }

allows(user) {
        var experiment = new Experiment("widget-permissions");
        experiment.use(() => this.model.checkUser(user).valid); // old way
        experiment.try(() => user.can(Permission.Read, this.model)); // new way

return experiment.run();
    }
}
```
Use `use(..)` to wrap the existing original behaviour, and use `try(..)` to wrap the new behaviour. `experiment.run();` will always return the result of the `use` block, but it does a bunch of stuff behind the scenes:

- It decides whether or not to run the `try` block
- Randomises order to execute `try` and `use` blocks
- Measures the duration of both behaviours
- Swallows (but records) any exceptions raised in the `try` block and
- Set a condition to filter calls to `try`

Upcoming features (these already exist in the `Ruby` library):
- Compares the result of `try` to the result of `use`,
- Publishes all this information.

The `use` block is called the **control**. The `try` block is called the **candidate**.