MOT Testing - Service Assessment
...and the face to face support available through DVSA’s 'Change agents'. It was good to hear how the team have actually pared down other activities to free up face-to-face support...
...and the face to face support available through DVSA’s 'Change agents'. It was good to hear how the team have actually pared down other activities to free up face-to-face support...
...code from the Alpha so that other people could learn from it and that the team had a clear policy of open by default for the beta code, with a...
...checks within the code, but any sensitive code should be managed and kept private whilst all other code should, by default, be open source. We would particular urge the team...
...understand and comment on. We decided to use Jupyter Notebook to document our experiments, because it allows us to write both code and free-form text, and expose the notebook via...
...code open and reusable. Although work is underway to make code from other components of the PAYE service available via a public GitHub it would be good to see code...
...etc. Open Source Code The panel were encouraged to hear HMRC are making progress in this area, but we are still yet to see any service code published. Publishing source...
...code open and reusable- point 15 The service team should continue the work to open their source code. Testing the end to end service - Point 17 Ensure the service...
...team to follow and for other teams to emulate. They explained how they now have a fully functioning development environment with integrated testing. Their process for getting code deployed is...
...explanation as to why this can’t be done for specific subsets of the source code). Code from the service has been published and is currently being reused by another government...
...open source code but recommend that the team should aim to publish all source code and should not attempt to evaluate usefulness. By doing this the SFA can allow other...