QASource Blog

As per many software testing experts, code coverage is a good way to identify the untested code. But the percentages aimed do not necessarily contribute to test quality. Such coverage goals encourage poorly designed tests, written with the only intention of meeting system requirements instead of testing the software correctly. We agree that unit testing is important but when aiming at quality its limited. A useful alternative is functional test coverage through test automation, which tracks whether tests execute important values or sequences of values corresponding to software features.

Enterprise Content Management is a kind of revolution which not only makes centrally stored files secure, allows document versioning, and content search, but also provides a provision to manage them easily. The Enterprise Content Management can be on cloud or setup locally. Stored files can be official documents in .xls, .doc, .ppt, .pdf file formats or multimedia files like video clip, audio file, and many more. SharePoint, Google Drive, Dropbox, and Box are some of the central storage repositories. Storing heavy files in bulk is of no use if it delivers at a slow pace. Hence, performance testing is required to verify the functionality under heavy load, session management, and stress capabilities. This time, we avail an opportunity to share our experience with Enterprise Content Management system.

Keep exploring more on performance testing with our quarterly performance testing newsletters.

Continuous integration is a practice to test every change of code done in repository. Further, the process of Continuous Deployment of builds help in achieving the Sprint targets on time. Faster builds speed up the whole system and minimize the integration issues.

As a conclusion, we can say that Continuous deployment of builds save time for both Dev and QA teams.

We all know, that the first generation of UI automation tools are ruling the market since last two decades and most commonly the automation engineers manually identify the UI elements to develop the automation test scripts in these tools. The main challenges being faced by most of the automation engineers is the maintenance of test scripts in-case of UI changes and ensuring the maximum test coverage through automation testing. To solve these challenges there is a second generation of automation tools which entered the market, which are smart enough to automatically adapt the test scripts in-case of UI changes and also, develop own test scenarios based upon the flows automated the user. So, our current newsletters will discuss about such tools.

The "Internet Of Things" is leading to a tremendous change in the world by enabling connection of devices, sensors and appliances with huge exchange of data. This requires new learning verticals for the performance testers to evaluate the performance of any IOT eco-system.

We have gathered some useful information which can help you to understand the change in performance testing approach and the areas of learning before commencing performance testing of IOT eco-system.

We continue to support our community with useful tips and knowledge base. Keep exploring more on performance testing with our quarterly performance testing newsletters.