ssciwr / ssciwr/effective-software-testing
sharing code effectively
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
In the coding session the way code was displayed on screen wasn't ideal:
- can only show a small part at a time for it to be readable
- people want to look at different parts at different times
- if someone gets stuck with an error it is hard for them to make progress & catch up
Maybe better?:
- have a shared jupyter notebook
- I copy & paste code chunks into cells
- they can have this open and copy&paste / read as they want
Alternative is to commit&push but not sure that is better - maybe ok if they have the branch open in a web browser? Don't want to complicate things wtih multiple branches
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reviewing the existing coding-session materials and deciding between a shared Jupyter notebook and branch-based sharing. Done means an agreed workflow is documented and usable when attendees need to inspect code or recover from an error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook, python
- Domain
- content, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100