French (Fr)English (United Kingdom)
  • News
  • Download
  • Contact me
  • Forum
SAT Welcome Basic principles

SAT

  • Welcome
    • Basic principles
    • Why to automate?
  • News
  • Download
  • How to participate?
  • Contributions
  • Links
  • Awards

Connexion

We have 2 guests online

Session



  • Forgot your password?
  • Forgot your username?
  • Create an account

Visitor counter

mod_vvisit_countermod_vvisit_countermod_vvisit_countermod_vvisit_countermod_vvisit_countermod_vvisit_counter
mod_vvisit_counterToday51
mod_vvisit_counterYesterday42
mod_vvisit_counterWeek372
mod_vvisit_counterMonth266

Donate

Thank you for your donation.




Designed by:
SiteGround web hosting Joomla Templates
Basic principles

 SAT includes an automated test management to ensure that software developed reflect the needs expressed in functional terms, quality and reliability. Automated functional testing is in fact an essential component of a comprehensive process of quality assurance software enables companies to accurately assess the quality of application functions and compliance with standards or industrial business and streamline processes critical but sometimes time-consuming.

The overall architecture of SAT is as follows:

The basic principles SAT differentiates from other products are:

Principle n°1

The test scripts using a scripting language simple and intuitive. These scripts are interpreted (not compiled) and all the tools developed are available:

  • Breakpoints,
  • Step by step mode,
  • Viewing and editing the value of variables at a standstill and running,
  • Speed performance configurable.

Principle n°2

Using the CLI (Command Line Interface) to interact with applications or equipment that you want to test. The CLI can be extended to the infinite possibilities of SAT simple intuitive way. A CLI is an application that has a standard interface (stdin / stdout / stderr) to communicate with SAT. A CLI can be developed and tested independently of TSS. Communication with the script is done through interface files consist of simple text files.

Principle n°3

With interfaces files, scripts can be independent of target applications to test these targets with the same interface definition but different hardware interfaces. This principle allows:

  • A reduction in the number of tests for a project,
  • An independent testing on the target to be tested (final target or simulator),
  • Reuse scripts on various projects.
 
Smart Automatic Test, Powered by Joomla! and designed by SiteGround web hosting