Improving Testing Workflows

With the adoption of any new technology comes a learning cycle, and to be candid Testnetic is no exemption. But over the next few articles ( maybe we should call it the Learning Series) we will illustrate how some of our users are improving testing workflows.

How developers and testers work together to some degree is affected by the development and testing environment. We will explore some approaches we have seen successfully employed.

Shared server for development and testing.

Here development and deployment conducted on the same server. Whilst naturally not the best practice it is quite common, especially for a startup. Typically development will be done locally and subsequently uploaded to a review and testing (staging) server. In our case initially development was reviewed on the developers local machine using screen sharing and chat tools such as Team Viewer or Skype. Once it look correct in development it is deployed on the testing server for functionality testing.

TestingOn demand servers such as Digital Ocean or Linode (our preference) make it simple to run up a server and are ideal for a startup. Naturally stage is accessed via an ip address. We have two projects on Testnetic called testing or staging and live. All testing is done and documented on the development server. Failed tests naturally go to Activities with comments and screen grabs when required. Once these failed tested are corrected by the developer they reassign the activity to the tester (done in Activities) and a further comments is made by the developer for the tester. This cycle continues until the work is completed to specification.

An advantage of Testnetic is the ability to add task. A task is simply an activity that does not need a test to be created. It can be created in an ad-hoc fashion.

Once an  Activity is completed to satisfaction then the tester can change the status to completed in Activities, with a comment. This signals developers to deploy the code to the live server, with a changed status of deployed. This signals the testers to immediately test on the live server.

Scheduling Times

At Testnetic we choose a window that enables fast upgrading of the code to production. We then review the live code against the changes that are documented in the most recent testing. Once this is signed off then it is onwards and upwards.

Good luck and if you have any questions or suggestions on improving testing workflows please reach out.

Share This Post

Share on facebook
Share on linkedin
Share on twitter
Share on email