In software development, integration is the process of combining individual software components into a single application. Continuous Integration (CI) is the practice of integrating new or changed code on a regular basis. Its purpose is to detect issuesearly in the development cycle. Instead of integrating code as part of a large, separate process toward the end of the implementation phase in the SDLC, CI aligns with Agile development by enforcing integration to occur frequently – at least once a day – thus enhancing agility and improving quality.
The Application Performance Management (APM) space has never been more important to organizations as it is today with so much of business profitability depending on fast, reliable web and mobile applications. At the same time, IT departments have never felt so much pressure to deliver on these applications with environment complexities not seen before, increased business demand, and all the while operating with shrinking budgets on manpower and infrastructure resources.
From the title, you may think this blog article is going to list a bunch of technical server metrics for performance testing, what they mean and their allowable ranges. I will leave that discussion for a future post. For now, we need to start at the beginning. We need to consider the ‘who’, the ‘why’ and the ‘what’ behind the collection of metrics for performance testing.
Are you attached to your Mobile Device? What kind of device do you have? A high tech phone or a tablet I would imagine. Do you use it for work? Does your work give you a phone or tablet to use? Most of us use our mobile devices for both work and personal needs. I assume a lot of you check email on your phones, whether for business or personal reasons. Oh, and what about that Facebook thing….Over the past year, I have seen Facebook being used for both business and personal reasons. What about the various mobile business apps. I assume that your company allows you to add the app to your own mobile device or onto a device that is given to you by your company.
Performance testing (aka: load testing) has been like the technology it supports – constantly changing over the years. Testing started with mainframe applications, then client/server was all the rage, after that the internet changed the face of IT applications. What to expect next? Let’s look at how performance testing is evolving with these changes.