Translating 1238 words of Jest English to Indonesian Part 4

Project Details

Jest is used by Facebook to test all JavaScript code including React applications. One of Jest's philosophies is to provide an integrated "zero-configuration" experience. We observed that when engineers are provided with ready-to-use tools, they end up writing more tests, which in turn results in more stable and healthy code bases.

Jest parallelizes test runs across workers to maximize performance. Console messages are buffered and printed together with test results. Sandboxed test files and automatic global state resets for every test so no two tests conflict with each other.

Source

Source Language

English

Number of Words

I translate a total of 1238 words.

Translated Language

I contribute to Indonesian Language and translated the file 'MigrationGuide.md',
'MockFunctions.md', 'SetupAndTeardown.md', and 'docs/en/MoreResources.md'. The project is huge, it still needs 44517 words to translate.

Before Translation


  • MigrationGuide.md from 47%
  • MockFunctions.md from 24%
  • SetupAndTeardown.md from 38%
  • docs/en/MoreResources.md from 23%


After Translation


Links

Check my Activity in Jest
My Profile Activity as Translator
Project Profile Link
GitHub Project Link
Crowdin Indonesian Translation

Part1, Part2, Part3

Examples

For example, if both initializeCityDatabase and clearCityDatabase returned
promises, and the city database could be reused between tests, we could change
our test code to:

Sebagai contoh, jika kedua initializeCityDatabase dan clearCityDatabase mengembalikan promise, dan basis data kota dapat digunakan ulang diantara percobaan, kami bisa mengubah kode percobaan kami ke:

Often while writing tests you have some setup work that needs to happen before
tests run, and you have some finishing work that needs to happen after tests
run.

Seringkali saat menulis percobaan anda memiliki beberapa aturan pekerjaan yang harus dilakukan sebelum percobaan berjalan, dan anda memiliki beberapa penyelesaian pekerjaan yang harus dilakukan setelah percobaan berjalan.

Once the describe blocks
are complete, by default Jest runs all the tests serially in the order they were
encountered in the collection phase, waiting for each to finish and be tidied up
before moving on.

Setelah uraian blok lengkap, secara bawaan Jest menjalankan semua percobaan berturut-turut sesuai urutan yang mereka temui dalam fase pengumpulan, menunggu masing-masing untuk selesai dan dirapikan sebelum berlanjut.

If you have a test that often fails when it's run as part of a larger suite, but
doesn't fail when you run it alone, it's a good bet that something from a
different test is interfering with this one.

Jika anda memiliki percobaan yang sering gagal ketika dijalankan sebagai bagian dari deretan yang lebih besar, namun tidak gagal ketika anda menjalankannya sendiri, itu adalah sebuah taruhan yang baik bahwa sesuatu dari percobaan yang lain mengganggu yang satu ini.



Posted on Utopian.io - Rewarding Open Source Contributors

H2
H3
H4
3 columns
2 columns
1 column
Join the conversation now