The next Byte-sized RSE session, covering Integrated Development Environments (IDEs), will take place on Tuesday 28th March, 13:00-14:30 GMT.
The next Byte-sized RSE session, covering code style and linting, will take place on Tuesday 28th February, 13:00-14:30 GMT.
Our website will be at risk during maintenance today (18 January, 16:45–17:00), and you may experience some disruption using the website within that period. We apologise for any inconvenience.
The next Byte-sized RSE session, covering continuous integration, will take place on Tuesday 17th January, 13:00-14:00 GMT.
The next Byte-sized RSE session, covering testing your python code, will take place on Tuesday 13th December, 13:00-14:00 UK.
Following the success of the first Byte-sized RSE session in October, session 2, covering collaboration and code review via GitHub will take place tomorrow (Tuesday 15th November), 14:00-15:00 GMT.
Byte-sized RSE is a new series of short interactive tutorial sessions where you can learn key skills to improve how you write and manage your research software in just 1 hour! The first session will take place on Tuesday 18th October at 13:00 BST on Zoom.
This guide is the first in the Unit Testing for Scale and Profit series. In a project where changes are frequently made to research software, it is helpful to know that the code still works as expected. In our last two episodes, we looked at the benefits of having a set of unit tests and how we can use test parameterisation to write numerous tests efficiently. However, particularly with projects involving more than one contributor, it would be good to have assurance the software still works without everyone having to pull down all the changes and test them. In this guide, we'll be looking at…
Our website will be at risk during maintenance on Monday 9 May from 12:30 - 14:30 BST, and you may experience some disruption using the website within that period. We apologise for any inconvenience.
Subscribe to Steve Crouch
This guide is the second in the Unit Testing for Scale and Profit series. As our code increases in size and particularly complexity, we should expect our number of tests to increase too, which means more time writing tests. Fortunately there is something that can help with this burden which we'll look at in this guide: parameterised tests!