Quick tip: Syncing a part of your email to your timesheet

In Automation, Invoices on December 2, 2017 at 9:31 am

It is that time of the month.  Time-sheets are due every week/2 weeks/ or maybe once a month.  However the routine involves entering the number of hours, along with details of your work everyday.

As your daily routine should go, an email for a daily status is always sent.  This contains details of you work.  Scraping only these emails (at the end of your time-sheet period) and filling your time-sheet with it could avoid manual entry and a lot of last minute rush.

Syncing of only the daily status emails can be done. However the security concerns are understandable as most time-sheet applications are 3rd party apps.  So automatically backing them up and then scraping their content and syncing them to the time-sheet server or scraping and pasting them on the server could be a worthwhile effort.

Point: Write once (your daily status) copy it as many times.

Knowledge of Python or shell scripting could be very helpful.





Important tip: How to raise bugs automatically

In Automation, Tools on August 5, 2017 at 8:03 am

Congratulations! you just automated a suite of end to end tests for your application.  You run these tests for every build, look at the reports and everyone is happy.  Really?

The report contains failed tests too.  You need to raise bugs for that.  What does that involve?

  1. A suitable title
  2. Steps involved to reproduce the bug
  3. Provide information on: OS, Architecture, Browser version, Application Version, CPU information, Memory usage, Disk Usage, CPU usage
  4. Expected Results, Actual results, Screenshots, Logs

Test processes can be inundating  and exasperating for many testers leading to loss of motivation in Testing.  This is a hidden risk.

The aftermath of automated test execution is one such process. However help is at hand when you use the AutomatedBugRaiser






Are we headed towards Prediction Driven Development?

In Automation, Machine Learning, Prediction on December 2, 2016 at 12:49 pm

In a recent tweet about Sanity Testing,  I started thinking about certain Machine Learning tools in the market which seem to predict defects for various change requests submitted.

Now assuming that this defect prediction tool “actually works”,  it would become extremely useful to conduct an extended Sanity (in the least).  This would lead to major issues caused by the change requests to be resolved even before it gets to the hands of a tester, thereby saving money and time.  Changes keep happening up-to the last minute of a Product release, and this could well be another way to develop Software.

%d bloggers like this: