Testmatick

The check of any, not too simple queue requires the use of a whole group of tests. When should this be done – during system testing or low level component testing? If a node has only one incoming link, and we have reason to believe that this queue is managed by the component represented by this node, then we should

Read more

The simple implementation of a number of development projects aimed at improving the manufacturing process within one organization does not yet guarantee the creation of world-class software. If each team chooses its own path to improve the process or product, the process’s optimization will be random in nature. In this case, local optimization appears to be one of global optimization

Read more

It is noticed that some people turn out to be very good at testing their own programs. They have the ability to find errors even without using any testing methodology (such as boundary value analysis ​​or function diagrams). This is explained by the fact that a person with practical experience often subconsciously applies the test design method called the error

Read more

There are two fundamentally different approaches to system testing.   In the first case, system requirements are used to develop tests, for example, a test is written for each requirement in order to check whether this system requirement is met. This approach is especially widely used in the development of military and scientific systems, when the customer is fully aware

Read more

One of the biggest mistakes in mobile development is to release a new product to the public without performing preliminary tests on it.   First, if you learn about the errors and shortcomings in the application from negative feedback about your design, this is unlikely to have a positive effect on the number of the product’s installations. Secondly, if an

Read more

There is also a functional software size measurement methodology, which is based on the assumption that the productivity of software development is somehow related to the functionality. Areas of functionality that are taken into account are called information domain values, some of which are listed below:   Number of user inputs – counting the number of user entries. It takes

Read more

Requirements elicitation is an especially critical step in the requirements development process, when the needs and constraints of the project are identified by the stakeholders. The goal is to define the users requirements which are middle level statements of needs of a stakeholder (the two other levels are business requirements and functional requirements). These are tasks that users need to

Read more

The Software Error Estimation Program (SWEEP), developed by the Software Productivity Consortium, is a predictive tool for calculating the error rate, including estimating the percentage of hidden errors. A hidden error is any error that remains in the program product, i.e. such an error that exists, but not yet detected. The value of the SWEEP model is that it simplifies

Read more

In a certain sense, Node has much in common with other popular web servers, such as Internet Information Services (IIS) created by Microsoft or Apache HTTP server. But it is far more interesting to know what differences it has, so let’s start with this.   Similarly to Express, the Node approach to web servers is extremely minimalistic. Unlike IIS or

Read more

The Defect Analysis Group (known in some quarters as the group controlling changes made to the technical documentation) determines whether to correct the defect within the current release or to postpone it until future versions are implemented. If the development teams and testers conduct further analysis after the defect was fixed and conclude that the program code does not contain

Read more