Note email is not suitable for marks, which will instead be uploaded to your class git repository. Also note that the majority of my email is spam, and so reading email for me is mostly about deleting messages that don't come from strange addresses and/or don't have meaningful subject lines. Don't bother emailing attachments as for obvious security reasons, I don't open attachments -- if necessary, use your git repository to make available to me files that you might otherwise email. Also, use the course wiki if you have questions that are not specific to you, such as requests for clarification on assignments or exam questions -- I generally check the course wiki the first thing when I get in and am more likely to check it than my email during the day.
Ruby will be the main programming language for the course -- students are not required or expected to have prior Ruby experience. It turns out that the Ruby community has devoted a lot of effort to advocating and developing free tools to support various techniques in software quality assurance and testing -- making it ideal for practice tasks in this course. Most notable among the tools are the testing tool RSpec to promote Behavioral Driven Development; Mutant to evaluate the quality of testing; and Cucumber to promote Story Driven Development. Also notable are code quality tools like Reek (for detecting code smells) and Rubocop (for static code analysis). Both the RSpec and Cucumber systems can also be used for testing web applications via their interfaces to the Selenium web-application testing-framework.
Course material will be made available on the course Confluence wiki and practice work handed in with Git to the course BitBucket Git repository (see course web page for relevant links). [Should the Atlassian software (Confluence and/or BitBucket) fail, we will back up to a course web page and paper reports as done in previous years]
Note: git allows you to hand in work multiple times (and the web interface to BitBucket lets you verify that you really did hand it in). You should use it to upload frequently. Then you get the benefits of both an off site backup (in case your computer dies or you accidently delete the wrong file) as well as being sure you didn't forget to hand in (something a few students seem to always manage to do). While there is a marking gap between having a `perfect' assignment and handing in a buggy one, the marking gap between a buggy assignment and no assignment is much larger.
Generally people do well on this sort of exam, particularly if they take advantage of the opportunity to review the material before sitting the exam and getting any clarification needed on what the questions are saying. Although people often complete early, it is a mistake to not take the time to double check your work.