Automated testing on push in Git - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a Git hook that runs tests on push.

Git

cd .git/hooks && mv pre-push.sample [1]

Drag options to blanks, or click blank then click option'

Apre-commit

Bpre-push

Ccommit-msg

Dpost-commit

Attempts:

3 left

💡 Hint

Common Mistakes

Using pre-commit instead of pre-push

Renaming to a non-hook filename

Not moving the sample file

The pre-push hook runs before pushing commits, so renaming pre-push.sample to pre-push activates it.

2fill in blank

medium

Complete the script line to run tests automatically on push.

Git

#!/bin/sh

[1]

Drag options to blanks, or click blank then click option'

Anpm test

Bgit status

Cecho 'Push started'

Dls -l

Attempts:

3 left

💡 Hint

Common Mistakes

Using git status instead of running tests

Using echo which does not run tests

Listing files instead of testing

Running 'npm test' executes the test suite automatically during the push hook.

3fill in blank

hard

Fix the error in the hook script to stop push if tests fail.

Git

#!/bin/sh

npm test || [1]

Drag options to blanks, or click blank then click option'

Aexit 0

Bcontinue

Cexit 1

Dreturn

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'exit 0' which allows push even if tests fail

Using 'continue' or 'return' which are invalid in shell scripts

Not handling test failure at all

Using 'exit 1' stops the push if tests fail by returning a failure status.

4fill in blank

hard

Fill both blanks to check test results and print a message.

Git

#!/bin/sh

if npm test [1]; then
  echo [2]
else
  exit 1
fi

Drag options to blanks, or click blank then click option'

A&& echo 'Tests passed!'

B|| echo 'Tests passed!'

C&& 'Tests passed!'

D'Tests passed!'

Attempts:

3 left

💡 Hint

Common Mistakes

Using '||' which runs echo on failure

Not using echo to print the message

Putting the message without echo

Using '&& echo' runs the echo only if tests pass, printing the success message.

5fill in blank

hard

Fill all three blanks to create a pre-push hook that runs tests and stops push on failure.

Git

#!/bin/sh

[1] || [2]

exit [3]

Drag options to blanks, or click blank then click option'

Anpm test

Bexit 1

C1

D0

Attempts:

3 left

💡 Hint

Common Mistakes

Exiting with 1 even if tests pass

Not running tests before exit

Using wrong exit codes

The script runs 'npm test', exits with 1 if tests fail, and exits 0 if tests pass to allow push.

Practice

1. What is the main purpose of automated testing on push in Git workflows?

easy

A. To run tests automatically when code is pushed to catch errors early

B. To manually review code before merging

C. To delete old branches after pushing

D. To speed up the push command execution

Solution

1. Step 1: Understand automated testing on push

   Automated testing on push means tests run automatically when code is pushed to a repository.

2. Step 2: Identify the main benefit

   This helps catch errors early and keeps the project stable by preventing broken code from merging.

3. Final Answer:

   To run tests automatically when code is pushed to catch errors early -> Option A

4. Quick Check:

   Automated testing on push = run tests automatically [OK]

Hint: Automated testing runs tests on push to catch bugs early [OK]

Common Mistakes:

• Thinking it speeds up git push command
• Confusing with manual code review
• Assuming it deletes branches automatically

2. Which file is commonly used to configure automated tests to run on push in a GitHub repository?

easy

A. package.json

B. README.md

C. .gitignore

D. .github/workflows/ci.yml

Solution

1. Step 1: Identify configuration file for GitHub Actions

   GitHub Actions uses YAML files inside the .github/workflows directory to define workflows.

2. Step 2: Match file to automated testing on push

   The file .github/workflows/ci.yml typically contains instructions to run tests on push events.

3. Final Answer:

   .github/workflows/ci.yml -> Option D

4. Quick Check:

   GitHub Actions config = .github/workflows/ci.yml [OK]

Hint: GitHub Actions workflows live in .github/workflows/ [OK]

Common Mistakes:

• Choosing .gitignore which ignores files
• Selecting README.md which is documentation
• Picking package.json which is for Node.js dependencies

3. Given this GitHub Actions workflow snippet, what happens when you push code to the main branch?

name: CI
on:
  push:
    branches: [main]
jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - name: Run tests
        run: echo "Tests passed!"

medium

A. The workflow fails because 'run' command is invalid

B. The workflow runs only on pull requests, not on push

C. The workflow runs and prints 'Tests passed!' on every push to main

D. Nothing happens because branches is empty

Solution

1. Step 1: Analyze the trigger event

   The workflow triggers on push events to the 'main' branch as specified under 'on: push: branches: [main]'.

2. Step 2: Check the job steps

   The job runs on ubuntu-latest, checks out the code, then runs the command echo "Tests passed!" which prints that message.

3. Final Answer:

   The workflow runs and prints 'Tests passed!' on every push to main -> Option C

4. Quick Check:

   Push to main triggers workflow = prints message [OK]

Hint: Push to main triggers workflow with echo command [OK]

Common Mistakes:

• Thinking it runs only on pull requests
• Assuming 'run' command is invalid syntax
• Believing branches list is empty

4. You wrote this GitHub Actions workflow to run tests on push but it never runs:

name: Test
on:
  push:
    branch: main
jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - run: echo "Running tests"

What is the error?

medium

A. The 'run' command must be inside a 'steps' array

B. The key 'branch' should be 'branches' under 'push' to specify branches list

C. The 'uses' action 'actions/checkout@v3' is deprecated

D. The 'runs-on' value 'ubuntu-latest' is invalid

Solution

1. Step 1: Check the event trigger syntax

   The workflow uses 'branch' instead of 'branches' under 'push'. The correct key is 'branches' which expects a list.

2. Step 2: Understand impact of wrong key

   Because 'branch' is invalid, the workflow never triggers on any push event.

3. Final Answer:

   The key 'branch' should be 'branches' under 'push' to specify branches list -> Option B

4. Quick Check:

   Correct key is 'branches' not 'branch' [OK]

Hint: Use 'branches' (plural) under push, not 'branch' [OK]

Common Mistakes:

• Confusing 'branch' with 'branches'
• Thinking 'runs-on' value is wrong
• Assuming checkout action is deprecated

5. You want to run automated tests only when code is pushed to either the 'main' or 'develop' branches. Which is the correct snippet to add in your GitHub Actions workflow YAML to trigger on these pushes?

hard

A. on:
push:
branches:
- main
- develop

B. on:
push:
branch: ['main', 'develop']

C. on:
push:
branch: 'main, develop'

D. on:
push:
refs: ['main', 'develop']

Solution

1. Step 1: Understand correct YAML syntax for branches

   The 'branches' key expects a list of branch names, each on its own line or in a list format.

2. Step 2: Compare options

   on: push: branch: ['main', 'develop'] uses incorrect singular 'branch' key instead of plural 'branches'. on: push: branches: - main - develop uses the correct 'branches' key with standard YAML list format using dashes, which is widely used.

3. Step 3: Identify invalid options

   on: push: branch: 'main, develop' uses 'branch' (wrong key) and a string with comma, which is invalid. on: push: refs: ['main', 'develop'] uses 'refs' which is not the correct key for branches under push.

4. Final Answer:

   on: push: branches: - main - develop -> Option A

5. Quick Check:

   Use 'branches' with list syntax for multiple branches [OK]

Hint: Use 'branches:' with dash list for multiple branches [OK]

Common Mistakes:

• Using 'branch' instead of 'branches'
• Passing branches as a comma string
• Using 'refs' instead of 'branches'