fortran-unit-testing-lesson

A Carpentries style lesson for teaching unit testing in Fortran

https://github.com/ucl-arc/fortran-unit-testing-lesson

Science Score: 52.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
    Found CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
    Found .zenodo.json file
  • DOI references
  • Academic publication links
  • Academic email domains
  • Institutional organization owner
    Organization ucl-arc has institutional domain (www.ucl.ac.uk)
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (13.7%) to scientific vocabulary

Keywords

english fortran lesson pre-alpha testing
Last synced: 6 months ago · JSON representation ·

Repository

A Carpentries style lesson for teaching unit testing in Fortran

Basic Info
Statistics
  • Stars: 0
  • Watchers: 3
  • Forks: 0
  • Open Issues: 4
  • Releases: 0
Topics
english fortran lesson pre-alpha testing
Created 10 months ago · Last pushed 6 months ago
Metadata Files
Readme Contributing License Code of conduct Citation

README.md

The Carpentries Workbench Template Markdown Lesson

This lesson is a template lesson that uses The Carpentries Workbench.

Note about lesson life cycle stage

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.

Create a new repository from this template

To use this template to start a new lesson repository, make sure you're logged into Github.
Visit https://github.com/carpentries/workbench-template-md/generate and follow the instructions. Checking the 'Include all branches' option will save some time waiting for the first website build when your new repository is initialised.

If you have any questions, contact @tobyhodges

Configure a new lesson

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

  1. Make sure GitHub Pages is activated: navigate to Settings, select Pages from the left sidebar, and make sure that gh-pages is selected as the branch to build from. If no gh-pages branch is available, check the Actions tab to see if the first website build workflows are still running. If they're not running yet, you may need to manually enable them via the Actions tab. The branch should become available when those have completed.
  2. Adjust the config.yaml file: this file contains global parameters for your lesson site. Individual fields within the file are documented with comments (beginning with #) At minimum, you should adjust all the fields marked 'FIXME':
    • title
    • created
    • keywords
    • life_cycle (the default, pre-alpha, is the appropriate for brand new lessons)
    • contact
  3. Annotate the repository with site URL and topic tags: navigate back to the repository landing page and click on the gear wheel/cog icon (similar to ⚙️) at the top-right of the About box. Check the "Use your GitHub Pages website" option, and add some keywords and other annotations to describe your lesson in the Topics field. At minimum, these should include:
    • lesson
    • the life cycle of the lesson (e.g. pre-alpha)
    • the human language the lesson is written in (e.g. deutsch)
  4. Adjust the CITATION.cff, CODE_OF_CONDUCT.md, CONTRIBUTING.md, and LICENSE.md files as appropriate for your project.
    • CITATION.cff: this file contains information that people can use to cite your lesson, for example if they publish their own work based on it. You should update the CFF now to include information about your lesson, and remember to return to it periodically, keeping it updated as your author list grows and other details become available or need to change. The Citation File Format home page gives more information about the format, and the cffinit webtool can be used to create new and update existing CFF files.
    • CODE_OF_CONDUCT.md: if you are using this template for a project outside The Carpentries, you should adjust this file to describe who should be contacted with Code of Conduct reports, and how those reports will be handled.
    • CONTRIBUTING.md: depending on the current state and maturity of your project, the contents of the template Contributing Guide may not be appropriate. You should adjust the file to help guide contributors on how best to get involved and make an impact on your lesson.
    • LICENSE.md: in line with the terms of the CC-BY license, you should ensure that the copyright information provided in the license file is accurate for your project.
  5. Update this README with relevant information about your lesson and delete this section.

Owner

  • Name: UCL Advanced Research Computing Centre
  • Login: UCL-ARC
  • Kind: organization
  • Location: United Kingdom

Citation (CITATION.cff)

# This template CITATION.cff file was generated with cffinit.
# Visit https://bit.ly/cffinit to replace its contents
# with information about your lesson.
# Remember to update this file periodically, 
# ensuring that the author list and other fields remain accurate.

cff-version: 1.2.0
title: Unit Testing in Fortran
message: >-
  Please cite this lesson using the information in this file
  when you refer to it in publications, and/or if you
  re-use, adapt, or expand on the content in your own
  training material.
type: dataset
authors:
  - given-names: Connor
    family-names: Aird
abstract: >-
  This lesson aims to teach the basics of writing unit tests in Fortran
  using a set of available frameworks - pFUnit, test-drive and veggies.
  The lesson will cover the basics of unit testing, how to identify and
  write testable Fortran code, how to write the unit tests for both
  serial and parallel Fortran in all three frameworks and how to
  integrate these tests into a Fortran project using both CMake and FPM
  build systems.

  This lesson is aimed at learners who already understand the basics of
  programming in Fortran and wish to start increasing the maintainability
  of their code with the addition of unit tests.
license: CC-BY-4.0

GitHub Events

Total
  • Issues event: 14
  • Delete event: 8
  • Issue comment event: 8
  • Member event: 1
  • Push event: 69
  • Pull request review event: 5
  • Pull request review comment event: 11
  • Pull request event: 10
  • Create event: 13
Last Year
  • Issues event: 14
  • Delete event: 8
  • Issue comment event: 8
  • Member event: 1
  • Push event: 69
  • Pull request review event: 5
  • Pull request review comment event: 11
  • Pull request event: 10
  • Create event: 13

Issues and Pull Requests

Last synced: 9 months ago

All Time
  • Total issues: 7
  • Total pull requests: 3
  • Average time to close issues: N/A
  • Average time to close pull requests: about 4 hours
  • Total issue authors: 1
  • Total pull request authors: 1
  • Average comments per issue: 0.0
  • Average comments per pull request: 1.0
  • Merged pull requests: 1
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 7
  • Pull requests: 3
  • Average time to close issues: N/A
  • Average time to close pull requests: about 4 hours
  • Issue authors: 1
  • Pull request authors: 1
  • Average comments per issue: 0.0
  • Average comments per pull request: 1.0
  • Merged pull requests: 1
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
  • connoraird (11)
  • dpshelio (1)
Pull Request Authors
  • connoraird (9)
Top Labels
Issue Labels
Pull Request Labels

Dependencies

.github/workflows/pr-close-signal.yaml actions
  • actions/upload-artifact v4 composite
.github/workflows/pr-comment.yaml actions
  • actions/checkout v4 composite
  • carpentries/actions/check-valid-pr main composite
  • carpentries/actions/comment-diff main composite
  • carpentries/actions/download-workflow-artifact main composite
.github/workflows/pr-post-remove-branch.yaml actions
  • carpentries/actions/download-workflow-artifact main composite
  • carpentries/actions/remove-branch main composite
.github/workflows/pr-preflight.yaml actions
  • carpentries/actions/check-valid-pr main composite
  • carpentries/actions/comment-diff main composite
.github/workflows/pr-receive.yaml actions
  • actions/checkout v4 composite
  • actions/upload-artifact v4 composite
  • carpentries/actions/check-valid-pr main composite
  • carpentries/actions/setup-lesson-deps main composite
  • carpentries/actions/setup-sandpaper main composite
  • r-lib/actions/setup-pandoc v2 composite
  • r-lib/actions/setup-r v2 composite
.github/workflows/sandpaper-main.yaml actions
  • actions/checkout v4 composite
  • carpentries/actions/setup-lesson-deps main composite
  • carpentries/actions/setup-sandpaper main composite
  • r-lib/actions/setup-pandoc v2 composite
  • r-lib/actions/setup-r v2 composite
.github/workflows/update-cache.yaml actions
  • actions/checkout v4 composite
  • carpentries/actions/check-valid-credentials main composite
  • carpentries/actions/update-lockfile main composite
  • carpentries/create-pull-request main composite
  • r-lib/actions/setup-r v2 composite
.github/workflows/update-workflows.yaml actions
  • actions/checkout v4 composite
  • carpentries/actions/check-valid-credentials main composite
  • carpentries/actions/update-workflows main composite
  • carpentries/create-pull-request main composite