My previous work at TechTime Initiative Group LimitedThe goal for my first month was to create a data source which could be used for load testing, with over 70,000 unique entries. To gather the information, we needed to interact with a website, ultimately we chose to use the end to end testing framework "Cypress". When working at such a large scale, individual tests which worked in isolation needed to be refined to work as a group of 10 tests. Here we overcame flakiness with alternative inputs. As we scaled to 100s of tests we needed to work with an external data source, to be looped across the sources for the test, and for results to be collected and compared. As we scaled to 1000s of tests, as a single computer was unable to run all the tests in a single suite, we needed it to be broken into different test files. Once we had a system that could potentially run all the tests, to reduce the run time, we scaled across multiple VMs. Scaling across multiple VMs needed for all the computers to be configured, to have the input data chunked into batches, and finally to have the output data retrieved and cleaned. This task taught me how to manage efficiently working together with others to get a big task done.Over the weekends I learnt from TechTime’s Tester about how a tester works with a development team to produce reliable software. The weekdays I spent with the development team, alerting them when bugs were found in the current project.After nearly two months of testing, a restructure saw my role transitioning into development. I learnt about the different mindsets one must have to be a developer compared to a tester. I created pull requests into the master branch of my work and learnt how to code in a professional environment. I had even accidentally pushed code that broke tests into the master branch, which I worked frantically with another member of the development team to resolve as fast as possible. This gave me insight into the mind of a professional when it came to debugging issues that come up.