Today we will examine the connection between testing processes and the design process, and also explore approaches to designing tests.
Earlier we considered the concept of Robotic Process Automation, where it makes sense to apply it, and where it is impractical. It’s time to talk about how this technology will evolve further and affect the moral aspect of replacing people with software robots.
In this part we will talk about how to monitor changes in configurations and what tools are used for this. In addition, it will be shown how SCM practices determine the order of tracking changes when working in a team. Also, we will not ignore some formal things, such as collecting metrics and documenting SCM activities.
Previously we’ve figured out what Robotic Process Automation is. Now let’s try to determine which processes are possible and should be robotized, which is not very advisable, and which – robots, in general, do not lend themselves.
We continue the series of articles about Software Configuration Management. Recall that Software Configuration Management (SCM) is the management of work product sets and their versions. In this part, we will pay attention to the configuration for component development and configuration of product lines.
Robotic Process Automation (RPA, Robotics) is a revolutionary technology that allows organizations to significantly increase operational productivity by replacing people with robots in order to redistribute the released human resource to perform more complex tasks that bring a large added value. From a technical point of view, it is a technology by which organizations configure software (software robots) to perform repetitive, mechanical operations at the user interface level. Software robots perform the specified operations in the same way that people do, receiving, sorting, processing data and performing certain actions with them, without changing the IT landscape of the organization.
So, we have defined the working products, components, rulers. The development cycle begins. Work is on, working products appear, change, new components are created, rulers are divided. As always, at some point you want to stop, look back and understand – at what point the product is located, what and how has already been done, what are the plans. To get the full picture, you need to bring the development to some common denominator. From the point of view of management, this can be done in different ways – you can, for example, see the progress of work, get a cut of metrics, etc. – and further to make some decision concerning the distribution of tasks.
We continue to study the subject of software testing and everything that is associated with it. Today we will understand what manual, static and dynamic testing is.
We live in the 21st century and such a phenomenon as robots is familiar to us. Earlier, about 50 years ago, robots were something unusual, and we met them only in pages of fantastic books and magazines. Now robots are not news, and are found everywhere. For example, a washing machine is the same robot programmed to wash our things, or a multi-cook, and the computer is also a robot! Indeed, more and more new technologies are being invented by people to make their lives easier, and they are called robots, because simplification of people’s life is a trend of the present. But what are these robots and how do they affect our lives?
Work products are in any project. This can be marketing documentation, requirements for the final product, source codes, tests, support tools. What will be considered a working product depends on the project. Further, each product changes in time (this is the point of development), and these changes must be taken into account somehow: who, when, what exactly he contributed and why he did it. In other words, consider how the product versions appeared.
Software Configuration Management (SCM) is the management of work product sets and their versions. This process is the scope of SCM.