Node.js Translation to Spanish - (1008 words) (Part 51)

alt

Repository

Project Details

Node.js is an open-source, cross-platform JavaScript run-time environment that executes JavaScript code outside of a browser.

Node.js came into existence when the original developers of JavaScript extended it from something you could only run in the browser to something you could run on your machine as a standalone application.

In simple words, it's an open source execution environment for developing web applications, which is event-based, it uses the V8 engine to provide an execution environment that compiles and executes JavaScript at a higher speed. It is possible to run Node.js without any restriction on Windows, Linux and Mac OS X.

It should be noted that it is NOT a server language, this means that it executes code, so it could be understood as an interpreter.

Contribution Specifications

Node.js is currently being translated into 33 languages. I'm contributing to translate it into the Spanish language.

So far, we have managed to translate 51% of the project!

Translation Overview

I continue with the ChangeLog_V7.md folder

In my previous contributions, I explained what a changelog is about. A Changelog is a record of all the notable changes made to a project, it usually includes change records such as new features or bug fixes. It includes all the changes historically, although it is intended that a Changelog does not include all the changes, but rather it contains a list of notable changes ordered chronologically for each version of a project.

During this contribution, I finished translating the commits belonging to the version 7.1.0, and I started with the version 7.0.0

Examples:

English:

373e9f08af - benchmark: add benchmark for v8.getHeap*Statistics (James M Snell) #12681

Spanish:

373e9f08af - benchmark: añadir prueba de rendimiento para v8.getHeap*Statistics (James M Snell) #12681

Benchmarks are the tests that are performed, from a perspective, to determine how quickly a task performs a system in particular working conditions. If everything goes well, this should be the task:

The technology of the benchmarks uses one or more PCs or servers to act as petitioners. Each emulates the presence of a number of users and each one executes an automatic sequence of interactions with the application whose performance is tested. In general, a PC acts as a test manager, coordinating, compiling the metrics of each of the executors and accumulating the performance data for the realization of the reports.

English:

e696bc33eb - increase test coverage for lib/zlib.js (Rich Trott) #9366

Spanish:

e696bc33eb - test: incrementar la cobertura para lib/zlib.js (Rich Trott) #9366

A test coverage is a measure used to describe the degree to which the source code of a program is executed when a particular test suite runs. A program with high test coverage, measured as a percentage, has had more of its source code executed during testing, which suggests it has a lower chance of containing undetected software bugs compared to a program with low test coverage.

In this image we can see an example of the coverage summary of current coverage metric of a project, courtesy of a coverage tool of GSoC 2018 Jenkins projects.