Our services


 

Security Testing


Security Testing
 
Objectives
  • Robusteness of user's authorization methods
  • Confidentiality of protocols and services exposed
  • Vulnerability to attacks
Tools
  • Skipfish
  • Nmap
  • Kali Tools
  • WireShark
Methodologies
  • Scan for open ports or other points of attack
  • Analyse strength of encryption methods used
  • Simulate various types of attacks
  • IP Sniffing
  • Look for weaknesses in passwords files
Test entry criteria
  • User Requirements
  • System Requirements
  • Functional Requirements
  • Non-functional Requirements
  • Scenario use cases
Security Testing

Security Testing


 
Objectives
  • Robusteness of user's authorization methods
  • Confidentiality of protocols and services exposed
  • Vulnerability to attacks
Tools
  • Skipfish
  • Nmap
  • Kali Tools
  • WireShark
Methodologies
  • Scan for open ports or other points of attack
  • Analyse strength of encryption methods used
  • Simulate various types of attacks
  • IP Sniffing
  • Look for weaknesses in passwords files
Test entry criteria
  • User Requirements
  • System Requirements
  • Functional Requirements
  • Non-functional Requirements
  • Scenario use cases
 

Platform development


Platform development
 
Objectives
  • Automated test JIG design and development
  • Minimize execution time and human interaction
Tools
  • Java, Python, C#, Expect
  • DAQ tools, analog and digital I/O interfaces
Methodologies
  • Development team assigned interlocutor
  • Identify the tests that gather most functionalities
  • Identify production facilities testing constraints
  • Flexibility and adaptation to client requirements
  • Enforce the "Design for Testability" concept
Test entry criteria
  • DUT specification
  • Requirements specification
  • Close proximity with development team
Platform development

Platform development


 
Objectives
  • Automated test JIG design and development
  • Minimize execution time and human interaction
Tools
  • Java, Python, C#, Expect
  • DAQ tools, analog and digital I/O interfaces
Methodologies
  • Development team assigned interlocutor
  • Identify the tests that gather most functionalities
  • Identify production facilities testing constraints
  • Flexibility and adaptation to client requirements
  • Enforce the "Design for Testability" concept
Test entry criteria
  • DUT specification
  • Requirements specification
  • Close proximity with development team
 

Web functionality


Web functionality
 
Objectives
  • Assure the correct functioning of the application according to the required specifications
  • Functional validation of websites
Tools
  • Cucumber
  • Selenium
  • Jenkins
Methodologies
  • Manual and automated testing
  • Test case design for each functionality
  • Website tree navigation
Test entry criteria
  • Website functional specification
  • Website map
Web functionality

Web functionality


 
Objectives
  • Assure the correct functioning of the application according to the required specifications
  • Functional validation of websites
Tools
  • Cucumber
  • Selenium
  • Jenkins
Methodologies
  • Manual and automated testing
  • Test case design for each functionality
  • Website tree navigation
Test entry criteria
  • Website functional specification
  • Website map
 

web compliance


web compliance
 
Objectives
  • Evaluate the website's content regarding the visitor's experience. Avoid discrepancies due to given targets: platform, network or browser.
Tools
  • W3C - HTML, CSS validator
  • CodeBeautify - JavaScript validator
  • Whatwg – HTML validator
  • Tidy – HTML validator
  • Achecker – Web pages validator
  • IP traffic shaping tools
Methodologies
  • All pages on the website will be inspected, regarding: code conformance (html, css, javascript, php, etc… ); browser compatibility; page rendering speed; responsiveness; for each intended use scenario.
Test entry criteria
  • Access to a working website server or a physical one and the necessary credentials
  • List of known constraints (network throughput, network delay, number of simultaneous clients,...) or typical intended use scenario
web compliance

web compliance


 
Objectives
  • Evaluate the website's content regarding the visitor's experience. Avoid discrepancies due to given targets: platform, network or browser.
Tools
  • W3C - HTML, CSS validator
  • CodeBeautify - JavaScript validator
  • Whatwg – HTML validator
  • Tidy – HTML validator
  • Achecker – Web pages validator
  • IP traffic shaping tools
Methodologies
  • All pages on the website will be inspected, regarding: code conformance (html, css, javascript, php, etc… ); browser compatibility; page rendering speed; responsiveness; for each intended use scenario.
Test entry criteria
  • Access to a working website server or a physical one and the necessary credentials
  • List of known constraints (network throughput, network delay, number of simultaneous clients,...) or typical intended use scenario
 

repair


repair
 
Objectives
  • Repairs in warranty and out of warranty (screening, SW upgrade, mechanical repair, component level repair)
  • DOAs management
  • Refurbishing
Tools
  • Elaboration of a scenario for the development tests of the entire device
  • Test JIG design and development assistance, which can be either stand-alone or PC-based solutions.
  • Stable and consolidated processes
  • Strong knowledge of STB/HGW products
Methodologies
  • Functional tests (Black-box)
  • Structural tests (White box)
  • Regression tests Integration tests Acceptance tests (UAT)
  • System tests GUI tests
  • Performance tests: - Load tests - Stress tests - Capacity tests
  • Maintainability tests Usability tests Security tests Automated tests
Test entry criteria
  • Real time Diagnosis
  • Real-time Test
  • Visual inspection and verification of connections unit per unit
  • Versatility and flexibility to adapt our facilities to new equipments
repair

repair


 
Objectives
  • Repairs in warranty and out of warranty (screening, SW upgrade, mechanical repair, component level repair)
  • DOAs management
  • Refurbishing
Tools
  • Elaboration of a scenario for the development tests of the entire device
  • Test JIG design and development assistance, which can be either stand-alone or PC-based solutions.
  • Stable and consolidated processes
  • Strong knowledge of STB/HGW products
Methodologies
  • Functional tests (Black-box)
  • Structural tests (White box)
  • Regression tests Integration tests Acceptance tests (UAT)
  • System tests GUI tests
  • Performance tests: - Load tests - Stress tests - Capacity tests
  • Maintainability tests Usability tests Security tests Automated tests
Test entry criteria
  • Real time Diagnosis
  • Real-time Test
  • Visual inspection and verification of connections unit per unit
  • Versatility and flexibility to adapt our facilities to new equipments