Table of Contents

[hemmerling] Testing

Related pages:

Organizations

Fairs, Conferences, Events

Certification

Testing Experts

Crowdtesting Jobs

Basics

Questions about the Testing of Embedded Software

  1. How to test embedded software ? Under the conditions
    1. Most of the code is machine-dependent, i.e. a function to be tested accesses hardware ( reads and writes registers, while the results depend on external conditions and events ).
    2. Resources ( RAM,.. ) are limited, in comparison to the well-known standard of deskop PCs.
    3. Use of standard ( free, OpenSource, commercial )Test frameworks and especially Unit Test frameworks.

Mockup - Simulation of Objects

Unit Test vs Functional Test

Keyword-based Testing

Test-First Approach - UX-Driven Testing

Test-First Approach

UX-Driven Testing

Property-based Testing

Scala ( and Java )

Haskell

F#

Javascript

Instrumentation Frameworks for Dynamic Application Testing

Test Mangement, Functional Test Tools, Automation Frameworks, GUI Testing Tools / Capture & Replay Tools

Important Dynamic Code Analysis Tools / Tools for Dynamic Analysis Security Testing ( DAST ), according to VDC Research in 2015, 2016-08, 2018-08

Some other General Test Management Tools

Testdata Creation and Testdata Management

Methods

Software

Integration & Automation Frameworks, Tools for functional Tests and Regression Tests

.NET

Java, Python, Web,..

Free GUI Testing Tools / Capture & Replay Tools

Windows, MacOSX, Linux, iPhone, Android

.NET

Java

Linux, X Window

PowerShell

Python

Tcl/Tk

Web / HTML Testing in Python, Java, Javascript, PHP

Appium
Javascript Tools
Katalon Studio
Playwright
Selenium
Selenium with Geb
Selenium with Codeception
SOAPSonar
SoupUI
Some other Tools
Online Services

Web Automation by direct HTTP Automation

Windows Macro Recorders

Basics
Tools

Windows Automation & Batch Systems

Macro Recorders in Desktop Applications

The Macro Recorder in OpenOffice

Just-Commercial GUI Testing Tools / Capture & Replay Tools

Web, Windows, WPF, HTML5, Flash, Flex, Silverlight, .NET, VCL and Java

Java & Web

.NET

Windows & Windows GUI

Windows Macro Recorders

Basics
Tools

Windows Automation & Batch Systems

Macro Recorders in Desktop Applications

The Macro Recorders in Microsoft Excel
The Macro Recorder in Microsoft Visual Studio
The Macro Recorder in Microsoft Word

Addons

OpenSource Software for End-to-End Testing of Databases

ORAYLIS BI.Quality

NBi

The Tool
Resources

Unit Test for Databases

Just-Commercial Software for Testing & Test Management

Just-Commercial Online Services for Testing & Test Management "In the Cloud"

Model-based Testing of Embedded Control Systems

Resources

Test Anything Protocol ( TAP )

TTCN-3

Commercial TTCN Testing Tools

Resources

YAML - YAML Ain't Markup Language, RAML, TAML,...

YAML Resources

RAML ( RESTful API Modeling Language )

YAML Software

Free YAML Online Services

TAML

Tools

Resources

Dynamic Code Analysis

Test Concept for Embedded Systems

Test Concept #1 - One-way Communication

Test Concept #1 - The classical "printf()"

Test Concept #1.2 - "Spy" Function of an RTOS

Test Concept #2 - Unit Test with Hardware Emulation

  1. Write a test for any module that will exercise the function at edge and corner cases.
  2. If the module code accesses hardware in the production version,
    1. Either supply adequiate hardware signals to the device under test ( Hardware in the Loop ( HIL ) ).
    2. And / or emulate the hardware and its input and output ( just use an if-query not to access hardware if the code is tested, bzt
      1. to use predefined static values.
      2. to use calculated values.
      3. to use values provided by a state machine.
      4. or values transfered from a host, which generates the values by a script, a calculation or with the help of a state machine.
  3. You might use test concept #1 for one-way communication.
  4. Somehow you have to start your tests, by uploading code which executes the tests instead of executing the application.

Test Concept #3 - Script Languages

Test Concept #3.1 - Script Language on the Target

Test Concept #3.1.1 - Dialog by a classical Monitor
Test Concept #3.1.2 - Application-specific Script Language on the Target
  1. Design a “command language” and a parser to run on the device and its application under test, so that the interface to the module functions can be triggered with various values.
  2. The input to that device under test could be scripted.

Test Concept #3.2 - Script Language on the Host

  1. Install a script language ( Python, Perl,..) which can work by serial communications.
  2. The target “opens” a new console on the host and executes script command by its own output.

Test Concept #3.3 - Script Language both on the Host and the target

  1. Combine concept #3.1.2 and #3.2 to let interact 2 applications by a common interface and interface language.

Some other Test Concepts

Blinded Experiment

Magazines

Books

General

Books about Software Testing

Books about Code Review, Cross-Browser Testing ( and Load Testing )

Books about TTCN

Resources

GUI Testing

General

Objects for testing your own Web Automation skills

Implementations

Search for Resources

Resources

Windows Task Automation

Database Debugging

Testing Education & Certification Preparation

Chat / IRC Communities

Forums, Newsgroups, Communities


When this document changes ! Site Navigation ( My Business ! My Topics ! Imprint / Contact ! Privacy Policy ! Keyword Index ! ! Google+ Publisher "hemmerling" )