Xento is a product based organisation with more than 800 IT Professionals including 350+ PHP Professionals working with a healthy dose of creativity and innovation. We promote an open atmosphere, where team members freely voice new ideas and are involved in all phases of our growth. At Xento, working is not just work; it's fun. Nurturing individual talent, fostering team work and recognition are the key elements of the Xento Culture.

How Load testing is different from Stress testing

Category: Continuous Improvement, Software Quality

load /amp; stress testing are part of performance testing

Hello Readers! In this world of software testing, we might have come across terminologies like performance testing, load testing, stress testing, etc.

At times these terminologies are interpreted to be the same term, but, they are different. Hence it is very important for a QA to understand the significant difference between these three types of testing.

In this blog, we will try to understand the actual difference between these types. continue

Localization, Internationalization and Globalization in Software

Category: Continuous Improvement, Software Quality

Internationalization in software

Localization: Localization (also referred as “L10N”, where 10 is the number of letters between L and N in the English word.) is the process of adapting a product or service to meet the needs of a particular language, culture or desired population’s “look-and-feel”.


Importance of Feasibility Study for Test Automation

Category: Continuous Improvement, Software Quality


We are in the era, where test automation is being utilized in most of the application development projects. Test automation is being carried out as a support activity for the manual test process, which will help to cut off the testing time and also reduce the testing budgets. The benefits of test automation will be reached in the long run where scripts will be executed continuously along with the sprints of an agile development process.

A test automation project should be started carefully with a good feasibility study. If we implement test automation without a proper study, it will provide deadly nightmares to the project and even to the organization. During the feasibility study, we should look at every aspect before commencing the actual project. There are several things that we should look upon. The most important one is conducting a Proof of Concept (POC). continue

User Experience (UX) a balancing act for your business

Category: Continuous Improvement, Software Quality

Xento - The Balance Act

Generally, users have a misconception about UX, as it is a process focused on visual design or UI design. In reality, UX is far bigger than what the users normally think about, it is a combination of a variety of disciplines that actually helps in enhancing the customer’s satisfaction of your products (i.e. virtual and physical). It is the ultimate key that is directly proportional to the increase in sales of your product or gaining customer satisfaction. It is the realization that a product or business success is not only the ability to meet customer’s need but it should be flawlessly and can be achieved by improved UX standards. continue

Agile For All

Category: Continuous Improvement, Software Quality


Well, if you are a techie or enthusiastic about technology, you might have heard about “Agile” and “Scrum.” if not then the obvious question asked would be what is Agile and Scrum? Agile development is an umbrella term for a set of methods and practices based on the values and principles as expressed in the Agile Manifesto, which includes Extreme Programming (XP), Scrum, Crystal, Dynamic Systems Development Method (DSDM), Lean Development and Feature-Driven Development (FDD). It has evolved features like transparency, collaboration, self-organization, and cross-functionality of teams. According to a survey held in US and UK after analyzing near about 1027 projects, 82% of failed projects cited waterfall practices as the cause of failure. To overcome the problems faced like; constantly changing requirements, a dependency of the previous phase or next phase, underestimation of time & cost, incorrect progress report by using traditional waterfall model. So Agile was introduced and the most popular and widely used framework of Agile is Scrum.


Shift Left- Testing approach

Category: Software Quality

Shift left a unique testing approach

Shift left  testing is an approach in which software and system testing is performed earlier, in each phase of the project/product life cycle.
As we know, the software development life cycle goes sequentially in the order as:

Requirements => Design => Coding => Testing. So, if you start from the left to right, the testing phase is to the extreme of software development life cycle. “Bugs are cheaper when caught young, says Larry Smith, a well known expert, another reason why we should start testing at an earlier stage. This concept was introduced where testing/tester need to be integrated from inception of the projects / products.

The principle of ‘shift left’ supports the testing team to collaborate with all the stakeholders early in the software development phase to clearly understand the requirement, design, draft testcase and automation scripts  to help know where the software may fail and fix them at the earliest. continue

Reasons to choose automation in software testing

Category: Software Quality


Time and tide waits for none, a very familiar idioms we have come across since ages. Similarly when we compare time and money, more significance goes to time. Money can be earned but time lost is never reversed. So, to save time we need something which can give us a good ROI(returns on investment) which is automation.

In this blog I am concentrating on how integrating automation into business can be useful as a whole. The first reason which really makes us use automated tools is to save time. One can imagine if there are no transport facility how long it would have taken to commute from one place to another. Secondly, quality does matter. Let’s take an everyday example, in the world of e-commerce, if we order a shirt online and the quality comes up bad, no customer will return back to use the same site. The final aspect is money. Consider if an online shopping company offering 50% flat discount on a branded item, then everyone would prefer shopping online. continue

Home Automation or Smart Home

Category: Continuous Improvement, Software Quality

Xento - Smart Home Automation

There’s nothing more stressful than wandering if you forget your home keys or to switch off the lights. But these nagging fears can disappear with a mere swipe of a finger, transforming into a ‘Smart Home’. Some people call it as ‘Home Automation’ which is a technical advancement in technology and will be perfect in every aspect by giving more comfort, more security or Artificial Intelligence (AI) to your house.

According to technical experts, it is vital amidst building mechanical systems which specialize in providing automation to normal homes and helps to convert it into intelligent Homes. This field sometimes also known as ‘Domotics’.

Smart Homes can manage your day-to-day activities without the fuss of worrying about maintenance & energy consumption. Looks like the television makers of the 90’s hit show “The Jetsons” were visionaries of futuristic smart homes. This sitcom was an inspiration to what the world would look to be with help of robotics.

There are some real time examples present which indicates smart homes are coming into existence –

  1. There are devices available which will turn on/off your home lights by clicking a single button.
  2. The same holds with locking or unlocking doors, using keys are soon to be a thing of the past.
  3. Smart homes today have enhanced their safety feature by integrating surveillance camera controls to mobile devices.


Unit Testing and its Importance

Category: Continuous Improvement, Software Quality

Unit Testing - a software development process

Application is developed, assigned to QA. QA creates a sheet full of bugs to be fixed and shares with the developer. If you are a developer, you would ask QA various questions – What the heck is this? How in the world could this happen to me? Why did this happen? We have tested our “application”, with every possible scenario on “browser”. Bugs are popping in, and we are fixing them. It takes quality time to fix those bugs. Probably more time to fix bugs than developing the piece of code. Quite a few times, client reports silly bugs which is embarrassing.

It might be the same bug you fixed weeks back, or yesterday itself. Debugging is sometimes not taken seriously. When in hurry, instead of checking whole application, QA as well checks the known areas with a few random clicks on the site pages. This is frustrating for clients/end users. Have you worked into this sort of the problem which is faced by many? There is a solution for this – UNIT TESTING, to get out of miserable life, to make lives better. continue

Test Then Code

Category: Newsletter, Oct-2014, Software Quality

We all are doing testing in our day to day life. You must have shopped with a female, how many questions they ask before buy? Even too much bargain. I know, sometimes very frustrated, but if you see at the different side of the coin, they end up with very good deals.
In this article, I am focusing on this kind of approach for doing software testing.

“Test then Code” is the phrase which I came across while reading ISTQB advanced level syllabus. It’s nothing but the requirement based testing strategy.

For any application, most important part is user requirements. If requirements are captured correctly, then we can reduce significant number of defects in initial phase itself. continue