15
Feb

What Does Error Guessing Mean??

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

12
Feb

The Two Fundamentally Different Approaches to System Testing

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

7
Feb

Interesting Facts About Rapid Mobile App Testing

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

5
Feb

What Are The Goals of Functional Points Analysis?

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

31
Jan

How to Hear What the Client Says About Software Requirements

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

29
Jan

Software Error Estimation Program (SWEEP)

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

25
Jan

Node: A New Kind of Web Server

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

22
Jan

Defining Defect Status

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

17
Jan

Pseudo-Debugging Known as Bebugging / Modification

Pseudo-debugging (bebugging), which is one of the methods for modifying a program, is a way to determine the effectiveness of test strategies used in a project. Before proceeding to a pseudo-debugging, it is necessary to garner the support of both testers and developers. How would you answer the question often asked by the development manager: “When can you expect to

Read more

15
Jan

How One Can Detect Writing to Uninitialized Memory

There is nothing worse than an error that comes from nowhere and does not correspond to any code execution path. If you find yourself in this situation, it is most likely due to writing to uninitialized memory, also known as writing to a random address (wild write). The reason for such errors lies in the uninitialized pointer, which by chance

Read more