Software Testing tools

This will be a very very short post about tools related with Software testing.

The various types of test tools according to the test process activities are:

  1. Tool support for management of testing and tests:
  • Test management tools
  • Requirements management tools
  • Incident management tools
  • Configuration management tools
  1. Tool support for static testing:
  • Review process support tools
  • Static analysis tools (D)
  • Modelling tools (D)
  1. Tool support for test specification:
  • Test design tools
  • Test data preparation tools
  1. Tool support for test execution and logging:
  • Test execution tools
  • Test harness/ Unit test framework tools (D)
  • Test comparators
  • Coverage measurement tools (D)
  • Security tools
  1. Tools support for performance and monitoring:
  • Dynamic analysis tools (D)
  • Performance testing, Load testing and stress-testing tools
  • Monitoring tools

As we saw on one of our previous post, software testing is fundamental to know our projects have achieved its goals, so lets keep our hands worknig with the following tools:

For Java:

We know Oriented Object programming is one of the principal paradigms today to program, but here we have a tool for make your code in Java fail: JUnit.

JUnit is a unit testing framework for Java programming language. JUnit has been important in the development of test-driven development, and is one of a family of unit testing frameworks collectively known as xUnit, that originated with JUnit.

Features of JUnit

  • JUnit is an open source framework, which is used for writing and running tests.
  • Provides annotations to identify test methods.
  • Provides assertions for testing expected results.
  • Provides test runners for running tests.
  • JUnit tests allow you to write codes faster, which increases quality.
  • JUnit is elegantly simple. It is less complex and takes less time.
  • JUnit tests can be run automatically and they check their own results and provide immediate feedback. There’s no need to manually comb through a
    Continue reading "Software Testing tools"

Software Engineering Historayyy lmao

Back in the good ol’ days where I wasn’t born and maybe you weren´t either, I’m talking about the 50’s and 60’s, software was delivered by hand and tested for a few hours before they could have the results back. The first widely used programming language was Fortran by your holyness IBM in 1957, along with Cobol, released by the US Department of Defense in 1962. But the processes of making software were still very slow and people accepted that they didn’t have the best methods, which led to something they called a Software Crisis, so in 1968 a conference was organized to find better ways of doing programming magic. At this conference is were the roots of Software Engineering were finally established.

Over the following decades, the discipline of programming saw a familiar tension between the scientific field, who gave the ideas of how to solve engineering challenges, and the crafty men that solved the practical needs of an industry faced with real-life time and cost pressures. Over the time more ideas came around, at the 80’s Object Oriented Programming came up as well as the use of GUIs to make interaction with the machine easier.

The next years leading up to these days the computing power of the machines programmers used was increased significantly,  but many don’t see this as a good thing, because before you had to write code as efficiently as possible with the little things you had, and now with so much capacity and memory, the quality of code has been downgrading leading up to wasteful software. Even if this phenomenon is true, recent years have been when there has been such an incredible development in the software industries, with the introduction of the Cloud, APIs and almost every industry realizing that they needed online presence

Continue reading "Software Engineering Historayyy lmao"