The transformation is determined by the business needs, and the business needs vary wherever you are. Your industry determines the kind of data you deal with, and how it will need to be used. A medical database will need to find details of a patient’s medical records. A retailer may need to track all individual POS sales, both to watch the financial side, and to observe the impact on inventory. A voter registration database may need to give reports of people using various filters for marketing or polling. And each of these systems has different details of what kinds of source data it needs as input and how the output data needs to be queried, all of which need to be checked for data
published by Anonymous on February 1, 2016 - 17:15
Summary
Firstly, it is absolutely necessary to regression test those areas of the application that are not being changed. Just because the code isn’t changing, it doesn’t mean that a change elsewhere is not going to impact it. Of course, a proper impact analysis of a change should highlight other areas of the application that may be affected. However, as we all know, things get missed and the first time you know about it is when something goes wrong in production and impacts your ability to do business.
published by Anonymous on December 27, 2016 - 15:16
Continuous integration approach is very helpful for Agile projects. Nearly everyone has been using or at least considering to use it for Unit testing, isn't it right? But automated visual/CSS testing on Jenkins or other CI tool seems to be much less popular. Why it is so? First of all, you need to have a visual testing solution which is well-compatible with your CI tool of choice. Unfortunately, integrating them is typically not a simple task.
Our team has successfully implemented automated CSS testing on our Jenkins server with the help of Screenster, our QA automation tool which does not require coding and is free to try - on premise and in the cloud. It allows QA automation engineers to:
Meetings are an essential part of any business, but for software development teams, these events can be a major driver in how to improve operations and what needs to be done next. Agile methodologies utilize retrospectives after each sprint to go over the work completed in that time and use that information to guide the next sprint's objectives. These get-togethers have become so essential because they enable continuous innovation and can help teams deliver better quality products. Here are a few things that should be on your agenda to address in retrospective meetings:
Recent comments