Adactin to diversify service offerings

Software testing services company, Adactin, will soon be diversifying its offerings. Instead of just offering testing services, the company will be including SI integration services to its portfolio.

Adactin CEO, Navneesh Garg, who started the Australian Deloitte Fast 500 company, told ARN that the new offering is based on market demand.

“Our customers want us to grow in other areas as well. We have done some work in that space but we want to amplify it further. 10 per cent of our work this year has been in the integration services space so we want to take it as a different business unit.

“We want to set it up as a separate organisation so we can offer a more end-to-end solution to customers moving forward,” he said.

Adactin is a reseller for HP and IBM. It also has Neotys, Acunetix, and RadView under its portfolio. The company also does local work with NEC, Quay Consulting, and RXP Services. Adactin also has a partnership with Ingram Micro in Australia, distributing HP products which Adactin then takes to market.

According to Garg, the company also intends to increase its play in the Australian channel. It currently has a big play in the Federal Government and NSW Government space.

“Besides the government, we do a lot of work for the energy sector, financial companies, and IT vendors. Having said that, our solutions are vertical agnostic so our focus is on ERP implementation and CRM. Our core focus is services.”

With most of its customers being mid-segment companies or organisations, Garg said getting more enterprise segment customers is on its to-do list.

“The enterprise segment space is always competitive. But we see a gap in the market and we’re trying to bridge the gap between mid-segment and enterprise.

“We’re also seeing an increase in demand for local resources. Customers that used to outsource or offshore solutions are now seeking on-site or on-shore resources. They want more local representation. A lot of the changes we’re making are driven by this trend,” he added.

Adactin has offices in Paramatta, Melbourne, Canberra, and Auckland. Adactin currently employs 60 people across its four operations.

“Sydney has been our core market for the past few years but we’re now looking at growing our Canberra, Melbourne, and Auckland markets. The Sydney market still has a lot of scope for us but we want to extend business to these regions,” Garg said.

Garg started Adactin in Australia more than five years ago. Previously, he was working in India for Adobe Systems, HCL, and CresTech Software Systems.



Performance Testing on AWS Cloudwatch

Amazon CloudWatch is a service used for monitoring servers which run on Amazon Web Services (AWS). It enables users to have a real-time monitoring of AWS resources such as Amazon EC2 instances, Amazon EBS (Elastic Block Store), ElastiCache and Amazon RDS database instances. AWS provides metrics for CPU utilization, latency, and request counts; allowing users to custom the metrics to be monitored, such as the memory usage, transaction volumes or error rates. This application allows users to view their application behaviour with the statistics in a graph format.
AWS management console provides access to Amazon Cloudwatch. Within the console, we use the EC2 matrix. A matrix is created for each instance. An instance will have a unique instance id and an instance name and a metric name. In this article we will focus on the CPU Utilization Metric.
There are different alarms that can be created to monitor the metrics in your application. When we create an alarm we have to first decide on the Amazon CloudWatch metric which we want to monitor. Metric can be like the CPU utilization, throughput, queue length, etc. Next, we choose the evaluation period (e.g., 1min, 5 mins, 15 mins, 1hour, or 1 day) and a statistical value to measure (e.g., Average, Min, Max, or Sum). To set a threshold, set a target value and choose whether the alarm will trigger when the value is greater than (>), greater than or equal to (>=), less than (<), or less than or equal to (<=) that value.

Following is the Graph for CPU Utilization. The evaluation period is 5 mins. The trigger is CPU Utilization > 50 all through the evaluation period. This will remain in the alarm state until it no longer breaches the set threshold.











Pooja Dogra

Test Analyst

Adactin Group

Why your website be tested for SQL Injection?

SQL injection is one of the common techniques of attacks used by the hackers where malicious users can inject SQL commands into an SQL statement, via web page input.
SQL commands can be injected and alter SQL statement to compromise the security of a web application.

An Example:
SQL Injection Based on 1=1 is Always True
The intention of the code is to create an SQL statement to select a user with a given user id.
If the web application is made in such a way that there is nothing to prevent a user from entering “wrong” input, the user can enter some “smart” input like this:
SELECT * FROM Users WHERE UserId = 10 or 1=1
The above SQL is valid. It will return all rows from the table Users, since WHERE 1=1 is logically always true.
The above example will seem dangerous If the Users table contains names and passwords.

The SQL statement above is much the same as this:
SELECT UserId, Name, Password FROM Users WHERE UserId = 10 or 1=1

A smart hacker might get access to all the user names and passwords in a database by simply inserting 10 or 1=1 into the input box.

Web sites require constant access to the database. Firewalls provide little or no defense against SQL injection attacks. Antivirus programs are equally ineffective at blocking SQL injection attacks. They are intended to spot and stop an entirely different kind of incoming data.

The most commonly used SQL injection defense is made up of two components –
• Routine updating and patching of all servers, services and applications.
• Producing and using well written and well tested website code that disallows unexpected SQL commands.


Saarah Nadia

Test Analyst

Adactin Group

Agile Estimation and Planning – Planning Poker

Agile is not a process, it’s a philosophy or set of values to move quickly and easily. In this article I am going to discuss one of the effective agile planning and estimation method.

Planning Poker:

It is an Agile estimating technique which has become very popular in the last few years. Agile teams have taken advantage in using Planning poker cards as it is extremely simple to play and also powerful technique to extricate the collective wisdom of the team.

How to Play??

The basic rules are:

  • Each participant gets a deck of cards as shown in the fig 1.2 which represents a sequence of numbers or the Fibonacci sequence (1, 2, 3, 5, 8, 13, 21, etc.), which is more popular.
  • Product owner explains one User story from the Product Backlog to the team
  • Product owner answers all the relevant questions that the team have got about the User story.
  • Every participant selects a card which represents an estimate of the time, risk involved, complexity, and other relevant factors involved.
  • When everybody are ready with an estimate, all the cards are presented on a board for finalizing.
  • If there is a harmony /agreement on one particular number then the estimation is recorded and move to another User story.
  • Repeat the same process for all the User stories in the product Backlog as shown in the fig 1.3

Reasons behind the success of using Planning poker:


  • Estimates are done in groups, logic behind is simple – Each person in the team have different experience and different ideas, there by benefit of teams collective intelligence.
  • Strengthen collaboration by engaging entire team.
  • Creates harmony in estimating rather than having a single person control the estimate.
  • Reveal issues early through timely discussions for each story.


By following the correct process and making an estimate for each User story allows the team to understand clearly how much the team can deliver the working software at the end of each Sprint/iteration.


Hope you enjoyed reading…have a great day.


Sujatha Nalluri

Test Analyst

Adactin Group

Agile Projects: How should Test Teams Adapt ?

When quality assurance teams and management who have adopted Agile practices first put the ideas to work, they face a significant impediment in unlearning the traditional mind-set and practices that experience in traditional practices has instilled in them.

The following adaptation practice was documented after our experience in couple of key projects that moved to Agile methodology. These practices are a real life saver for project teams that are new to Agile.

The following are some of the key aspects that need to be unlearned before attempting to deploy Agile practices, from a QA perspective:


  • The testing team needs to be independent and independently empowered in order to be effective.
  • Without a separate test strategy and test plan, it’s tough to manage testing.
  • The V-model for verification and validation cannot be applied in an Agile sprint.
  • Independent testing teams don’t do white-box testing.
  • The value of testing is realized only when defects are logged.
  • Automation is optional and is required only when regression testing is needed.
  • Testing nonfunctional aspects, such as performance of the system, is not possible in a sprint.
  • Testing must follow planning, specification, execution, and completion sequentially.
  • We don’t have to write new test cases for detected defects.
  • Poorly written code is not the testing team’s focus, as long as the code addresses the required functionality.
  • Test-process improvement models do not address aspects of Agile testing.