GitHub Actions can run test and lint commands automatically on pushes and pull requests.
Understanding the Concept
GitHub Actions can run test and lint commands automatically on pushes and pull requests. A workflow typically checks out the repository, installs a supported Python version, installs project dependencies and executes verification commands.
In .github/workflows/python-tests.yml, configure actions/checkout, actions/setup-python with python-version 3.15, dependency installation and python -m unittest discover; review action versions.
How this fits into a real test suite
A reliable test starts with a specific expected behavior. Keep the fixture small, arrange the input, call the real code, and assert a result the reader can verify. Add one boundary or failure case so the test does not pass only for a convenient example. In a larger project, run the same test automatically after each change.
Tests are repeatable experiments. Use temporary resources and injected dependencies where possible; when the environment is part of the requirement, add a separate integration test rather than weakening the unit test.
Worked Example
Read the code from the first line to the last. Identify which values are inputs, which operation is being demonstrated and what should happen before running it.
import unittest
class ContinuousIntegrationTests(unittest.TestCase):
def test_math(self):
self.assertEqual(sum([2, 3]), 5)
print('CI command: python -m unittest discover')Walkthrough: What Each Part Does
- The imports make unittest available. These are standard-library building blocks unless the example explicitly names an external tool.
- The definition ContinuousIntegrationTests creates reusable behavior. Its body runs when called, awaited or instantiated; defining it alone does not run the body of an ordinary function.
- The final check compares actual behavior with an explicit expectation. A successful test tells you that this particular case passed, not that every possible input works.
This demonstration focuses on one practical behavior. Before changing several lines, vary one input or one configuration choice and check whether the result changes for the reason you expected.
The example uses terminal, platform, external tool or process behavior that was not exercised automatically. Run it only in a suitable environment after reviewing the shown permissions and paths.
Important Behavior and Edge Cases
Putting long-lived secrets directly into workflow YAML or allowing untrusted pull-request code broad write access.
In .github/workflows/python-tests.yml, configure actions/checkout, actions/setup-python with python-version 3.15, dependency installation and python -m unittest discover; review action versions.
Practice Exercise
Define a minimal test command that a CI workflow can execute.
Write down the result you expect before running your changed code. Check at least one normal case and one boundary or failure case. If your example starts workers or opens resources, verify how they are cleaned up.
Further reading: official documentation and API reference.
Common Beginner Mistakes
- Putting long-lived secrets directly into workflow YAML or allowing untrusted pull-request code broad write access.
- Writing assertions that check implementation details but fail to validate the behavior that matters to the caller.
Key Takeaways
- GitHub Actions can run test and lint commands automatically on pushes and pull requests.
- In .github/workflows/python-tests.yml, configure actions/checkout, actions/setup-python with python-version 3.15, dependency installation and python -m unittest discover; review action versions.
- Practice: Define a minimal test command that a CI workflow can execute.