본문으로 건너뛰기

레슨 7/13 · 18단어 · 외운 단어 0

Testing and version control

테스트와 버전 관리

  1. 1

    merge(verb)

    /mɜːrdʒ/

    병합하다, 머지하다, 통합하다

    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.

    리뷰가 끝나면 작업 브랜치를 main에 병합할 수 있습니다.

    The two customer databases were merged into a single system.

    유의어combineuniteintegrateconsolidateamalgamatefuseblend
    반의어separatedividesplitdissolvediverge
  2. 2

    repository(noun)

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

    저장소, 리포지토리

    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.

    리포지토리를 클론한 후 README 파일의 설치 안내를 따르십시오.

    Each microservice has its own repository on GitLab.

    유의어storehousearchivedepotdatabase
    반의어scatteringdistribution
  3. 3

    quality assurance(noun)

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

    품질 보증, 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.

    저희 품질 보증 팀은 모든 빌드를 고객에게 전달하기 전에 테스트합니다.

    He moved from quality assurance to software development last year.

    유의어quality controlQAtestingvalidation
    반의어quality neglectcarelessness
  4. 4

    version control(noun)

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

    버전 관리, 형상 관리

    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.

    모든 프로젝트 파일이 버전 관리 하에 있어서 아무것도 유실되지 않는다.

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

    유의어revision controlsource control
    반의어none
  5. 5

    software testing(noun)

    /ˈsɒftweə ˌtestɪŋ/

    소프트웨어 테스트, 소프트웨어 테스팅

    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.

    막판에 변경 사항이 많아 소프트웨어 테스트가 계획보다 오래 걸렸다.

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

  6. 6

    test case(noun)

    /ˈtest keɪs/

    테스트 케이스

    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.

    테스터는 새로운 결제 프로세스를 위한 테스트 케이스 40개를 작성했다.

    Two test cases failed, so the release was delayed.

  7. 7

    unit test(noun)

    /ˈjuːnɪt test/

    단위 테스트, 유닛 테스트

    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.

    모든 새 함수에는 단위 테스트가 함께 작성되어야 한다.

    The build failed because three unit tests did not pass.

  8. 8

    integration testing(noun)

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

    통합 테스트

    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.

    통합 테스트 결과 앱과 결제 게이트웨이가 데이터를 올바르게 주고받지 못하고 있는 것으로 나타났다.

    We do integration testing after each module is finished.

  9. 9

    regression testing(noun)

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

    회귀 테스트

    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.

    회귀 테스트에서 업데이트로 인해 검색 기능이 고장 난 것이 발견되었다.

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

  10. 10

    UAT(abbreviation)

    /ˌjuː eɪ ˈtiː/

    사용자 인수 테스트, UAT

    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.

    고객사는 다음 주에 UAT를 시작하고, 모든 것이 정상적으로 작동하면 승인할 것이다.

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

  11. 11

    bug report(noun)

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

    버그 리포트, 버그 보고서

    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.

    좋은 버그 리포트에는 스크린샷과 문제를 재현하는 단계가 포함되어 있다.

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

  12. 12

    code review(noun)

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

    코드 리뷰, 코드 검토

    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.

    모든 변경 사항은 최소 한 명의 시니어 개발자의 코드 리뷰를 통과해야 한다.

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

  13. 13

    refactor(verb)

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

    리팩터링하다, 리팩토링하다

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

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

    우리는 유지보수를 쉽게 하기 위해 오래된 결제 모듈을 리팩터링했다.

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

  14. 14

    Git(noun)

    /ɡɪt/

    깃, Git

    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.

    신입 개발자는 입사 첫 주에 기본적인 Git 명령어를 익혀야 한다.

    We use Git with GitHub to manage all our projects.

  15. 15

    branch(noun)

    /brɑːntʃ/

    브랜치, 분기

    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.

    작업하는 기능마다 새 브랜치를 만드세요.

    Never push untested code directly to the main branch.

  16. 16

    commit(verb)

    /kəˈmɪt/

    커밋하다

    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.

    변경 사항을 자주 커밋하고 메시지를 명확하게 작성하세요.

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

  17. 17

    merge conflict(noun)

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

    머지 컨플릭트, 병합 충돌

    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.

    둘이 같은 함수를 수정했기 때문에 머지 컨플릭트를 해결해야 했다.

    Pull the latest changes often to avoid merge conflicts.

  18. 18

    pull request(noun)

    /ˈpʊl rɪˌkwest/

    풀 리퀘스트, PR

    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.

    나는 풀 리퀘스트를 열고 동료 두 명에게 리뷰를 요청했다.

    The pull request was approved and merged this morning.