Skip to content

Commit c7542a9

Browse files
Add description and contents
1 parent 1410315 commit c7542a9

File tree

1 file changed

+19
-63
lines changed

1 file changed

+19
-63
lines changed

README.md

Lines changed: 19 additions & 63 deletions
Original file line numberDiff line numberDiff line change
@@ -1,72 +1,28 @@
1-
# The Carpentries Workbench Template Markdown Lesson
1+
# Python testing for research
22

3-
This lesson is a template lesson that uses [The Carpentries Workbench][workbench].
3+
A short course on the basics of software testing in Python using the `pytest` library.
44

5-
## Note about lesson life cycle stage
6-
Although the `config.yaml` states the life cycle stage as pre-alpha, **the template is stable and ready to use**. The life cycle stage is preset to `"pre-alpha"` as this setting is appropriate for new lessons initialised using the template.
5+
This lesson uses [The Carpentries Workbench][workbench] template.
76

8-
## Create a new repository from this template
7+
## Course Description
98

10-
To use this template to start a new lesson repository,
11-
make sure you're logged into Github.
12-
Visit https://github.com/carpentries/workbench-template-md/generate
13-
and follow the instructions.
14-
Checking the 'Include all branches' option will save some time waiting for the first website build
15-
when your new repository is initialised.
9+
Whether you are a seasoned developer or just write the occasional script, it's important to know that your code does what you intend, and will continue to do so as you make changes.
1610

17-
If you have any questions, contact [@tobyhodges](https://github.com/tobyhodges)
11+
Software testing is a methodology of automatically ensuring that your code works correctly, without having to go back and manually verify after each change.
1812

19-
## Configure a new lesson
13+
This course seeks to provide you with conceptual understanding and the tools you need to start ensuring the robustness of your code.
14+
15+
### Contents
16+
17+
- Basic tests
18+
- Running a test suite & understanding outputs
19+
- Best practices
20+
- Testing for errors
21+
- Testing data structures
22+
- Fixtures
23+
- Parametrisation
24+
- Testing file outputs
25+
- Continuous integration & automatic test-running with GitHub
2026

21-
Follow the steps below to
22-
complete the initial configuration of a new lesson repository built from this template:
2327

24-
1. **Make sure GitHub Pages is activated:**
25-
navigate to _Settings_,
26-
select _Pages_ from the left sidebar,
27-
and make sure that `gh-pages` is selected as the branch to build from.
28-
If no `gh-pages` branch is available, check _Actions_ to see if the first
29-
website build workflows are still running.
30-
The branch should become available when those have completed.
31-
1. **Adjust the `config.yaml` file:**
32-
this file contains global parameters for your lesson site.
33-
Individual fields within the file are documented with comments (beginning with `#`)
34-
At minimum, you should adjust all the fields marked 'FIXME':
35-
- `title`
36-
- `created`
37-
- `keywords`
38-
- `life_cycle` (the default, _pre-alpha_, is the appropriate for brand new lessons)
39-
- `contact`
40-
1. **Annotate the repository** with site URL and topic tags:
41-
navigate back to the repository landing page and
42-
click on the gear wheel/cog icon (similar to ⚙️)
43-
at the top-right of the _About_ box.
44-
Check the "Use your GitHub Pages website" option,
45-
and [add some keywords and other annotations to describe your lesson](https://cdh.carpentries.org/the-carpentries-incubator.html#topic-tags)
46-
in the _Topics_ field.
47-
At minimum, these should include:
48-
- `lesson`
49-
- the life cycle of the lesson (e.g. `pre-alpha`)
50-
- the human language the lesson is written in (e.g. `deutsch`)
51-
1. **Adjust the
52-
`CODE_OF_CONDUCT.md`, `CONTRIBUTING.md`, and `LICENSE.md` files**
53-
as appropriate for your project.
54-
- `CODE_OF_CONDUCT.md`:
55-
if you are using this template for a project outside The Carpentries,
56-
you should adjust this file to describe
57-
who should be contacted with Code of Conduct reports,
58-
and how those reports will be handled.
59-
- `CONTRIBUTING.md`:
60-
depending on the current state and maturity of your project,
61-
the contents of the template Contributing Guide may not be appropriate.
62-
You should adjust the file to help guide contributors on how best
63-
to get involved and make an impact on your lesson.
64-
- `LICENSE.md`:
65-
in line with the terms of the CC-BY license,
66-
you should ensure that the copyright information
67-
provided in the license file is accurate for your project.
68-
1. **Update this README with
69-
[relevant information about your lesson](https://carpentries.github.io/lesson-development-training/collaborating-newcomers.html#readme)**
70-
and delete this section.
7128

72-
[workbench]: https://carpentries.github.io/sandpaper-docs/

0 commit comments

Comments
 (0)