Saltar al contenido

Lección 7/13 · 18 palabras · 0 aprendidas

Testing and version control

Pruebas y control de versiones

  1. 1

    merge(verb)

    /mɜːrdʒ/

    fusionar, combinar

    to combine two or more things into one, such as joining changes from one branch of code into another

    After the review, you can merge your branch into main.

    Después de la revisión, puede fusionar su rama con main.

    The two customer databases were merged into a single system.

    Sinónimoscombineuniteintegrateconsolidateamalgamatefuseblend
    Antónimosseparatedividesplitdissolvediverge
  2. 2

    repository(noun)

    /rɪˈpɑːzətɔːri/

    repositorio

    a central place where files, especially a project's code and its history of changes, are stored

    Clone the repository and follow the setup guide in the README file.

    Clone el repositorio y siga la guía de configuración del archivo README.

    Each microservice has its own repository on GitLab.

    Sinónimosstorehousearchivedepotdatabase
    Antónimosscatteringdistribution
  3. 3

    quality assurance(noun)

    ˈkwɒlɪti əˈʃʊərəns

    aseguramiento de la calidad, QA

    the work of checking that products and processes meet agreed quality standards, often shortened to QA

    Our quality assurance team tests every build before it goes to the client.

    Nuestro equipo de aseguramiento de la calidad prueba cada versión antes de enviarla al cliente.

    He moved from quality assurance to software development last year.

    Sinónimosquality controlQAtestingvalidation
    Antónimosquality neglectcarelessness
  4. 4

    version control(noun)

    /ˈvɜːʃn kənˌtrəʊl/

    control de versiones

    a system that records every change to files, especially code, so teams can track and undo changes

    All project files are kept under version control, so nothing is lost.

    Todos los archivos del proyecto están bajo control de versiones, así que no se pierde nada.

    Version control lets us see who changed each line and when.

    Sinónimosrevision controlsource control
    Antónimosnone
  5. 5

    software testing(noun)

    /ˈsɒftweə ˌtestɪŋ/

    pruebas de software

    the process of checking that a program works correctly and meets its requirements before it is released

    Software testing took longer than planned because of many last-minute changes.

    Las pruebas de software tomaron más tiempo de lo planeado debido a los muchos cambios de último momento.

    She has five years of experience in software testing for banking apps.

  6. 6

    test case(noun)

    /ˈtest keɪs/

    caso de prueba

    a set of steps, input data and expected results used to check one function of a system

    The tester wrote forty test cases for the new checkout process.

    El tester escribió cuarenta casos de prueba para el nuevo proceso de pago.

    Two test cases failed, so the release was delayed.

  7. 7

    unit test(noun)

    /ˈjuːnɪt test/

    prueba unitaria

    a small automated test that checks one function or small part of the code on its own

    Every new function must come with unit tests.

    Cada nueva función debe incluir pruebas unitarias.

    The build failed because three unit tests did not pass.

  8. 8

    integration testing(noun)

    /ˌɪntɪˈɡreɪʃn ˌtestɪŋ/

    pruebas de integración

    testing that checks whether different parts or systems work correctly together

    Integration testing showed that the app and the payment gateway were not exchanging data correctly.

    Las pruebas de integración mostraron que la aplicación y la pasarela de pago no estaban intercambiando datos correctamente.

    We do integration testing after each module is finished.

  9. 9

    regression testing(noun)

    /rɪˈɡreʃn ˌtestɪŋ/

    pruebas de regresión

    testing again after a change to make sure that features which worked before still work

    Regression testing found that the update had broken the search function.

    Las pruebas de regresión revelaron que la actualización había dañado la función de búsqueda.

    We automated our regression testing to save time before each release.

  10. 10

    UAT(abbreviation)

    /ˌjuː eɪ ˈtiː/

    UAT, pruebas de aceptación del usuario

    user acceptance testing: the final testing stage, where real users check that the system meets their needs

    The client will start UAT next week and sign off if everything works.

    El cliente comenzará las UAT la próxima semana y dará su aprobación si todo funciona.

    Several issues were found during UAT, so go-live was postponed.

  11. 11

    bug report(noun)

    /ˈbʌɡ rɪˌpɔːt/

    reporte de errores, informe de errores

    a written description of a software problem, including how to reproduce it and what should happen instead

    A good bug report includes screenshots and the steps to reproduce the problem.

    Un buen reporte de errores incluye capturas de pantalla y los pasos para reproducir el problema.

    The tester filed a bug report about the broken export button.

  12. 12

    code review(noun)

    /ˈkəʊd rɪˌvjuː/

    revisión de código

    the process in which developers check each other's code for mistakes and quality before it is merged

    Every change must pass code review by at least one senior developer.

    Todo cambio debe pasar por una revisión de código realizada por al menos un desarrollador sénior.

    The code review found a security problem in the login logic.

  13. 13

    refactor(verb)

    /ˌriːˈfæktə(r)/

    refactorizar, reestructurar el código

    to improve the structure of existing code without changing what it does

    We refactored the old billing module to make it easier to maintain.

    Refactorizamos el antiguo módulo de facturación para que sea más fácil de mantener.

    Before adding new features, the team decided to refactor the messy code.

  14. 14

    Git(noun)

    /ɡɪt/

    Git, sistema de control de versiones

    the most widely used version control system, which tracks changes in code and helps teams work together

    New developers must learn basic Git commands in their first week.

    Los nuevos desarrolladores deben aprender los comandos básicos de Git en su primera semana.

    We use Git with GitHub to manage all our projects.

  15. 15

    branch(noun)

    /brɑːntʃ/

    rama rama de código, branch

    a separate copy of the code where a developer can work on changes without affecting the main version

    Create a new branch for each feature you work on.

    Crea una nueva rama para cada funcionalidad en la que trabajes.

    Never push untested code directly to the main branch.

  16. 16

    commit(verb)

    /kəˈmɪt/

    confirmar cambios, hacer un commit

    to save a set of changes to a version control system, with a short message describing them

    Commit your changes often and write clear messages.

    Haz commit de tus cambios con frecuencia y escribe mensajes claros.

    He committed the fix at midnight, just before the release.

  17. 17

    merge conflict(noun)

    /ˈmɜːdʒ ˌkɒnflɪkt/

    conflicto de fusión, conflicto de merge

    a situation where two people changed the same part of a file, so the system cannot combine the changes automatically

    I had to resolve a merge conflict because two of us edited the same function.

    Tuve que resolver un conflicto de fusión porque dos de nosotros editamos la misma función.

    Pull the latest changes often to avoid merge conflicts.

  18. 18

    pull request(noun)

    /ˈpʊl rɪˌkwest/

    solicitud de extracción, pull request

    a request to merge your code changes into the main project, so that others can review them first

    I opened a pull request and asked two colleagues to review it.

    Abrí una solicitud de extracción (pull request) y le pedí a dos colegas que la revisaran.

    The pull request was approved and merged this morning.