Cyrille Giquello

Outils pour utilisateurs

Outils du site

Vous êtes ici : accueil » informatique » php
Piste :
informatique:php

Différences

Ci-dessous, les différences entre deux révisions de la page.

Lien vers cette vue comparative

Les deux révisions précédentesRévision précédente
Prochaine révision		Révision précédente
informatique:php [14/07/2026 07:55] – [PHP_CodeSniffer] cyrilleinformatique:php [14/07/2026 08:05] (Version actuelle) – [intelephense] cyrille
Ligne 135: Ligne 135:
  
 ==== Phpstan ==== ==== Phpstan ====
 +
 +https://phpstan.org/user-guide/
  
 <code> <code>
Ligne 141: Ligne 143:
  
 ==== intelephense ==== ==== intelephense ====
 +
 +https://intelephense.com/docs
  
 <code php> <code php>
Ligne 148: Ligne 152:
  
 ==== phpUnderControl ==== ==== phpUnderControl ====
 +<WRAP center round important 60%>
 +phpUnderControl c'est terminé.
 +</WRAP>
 +
 +
 +  * [[http://phpundercontrol.org/|phpUnderControl]] - Continuous Integration for PHP.
 +  * https://github.com/phpundercontrol/phpUnderControl-UNMAINTAINED
  
-[[http://phpundercontrol.org/|phpUnderControl]] - Continuous Integration for PHP. 
   * Testing and software metrics, PHPUnit output: Code Coverage, Project Mess Detection and Software Metrics.   * Testing and software metrics, PHPUnit output: Code Coverage, Project Mess Detection and Software Metrics.
   * Documentation: PhpDocumentor, to generate an up to date documentation of the software on every build cycle. Therefore the developers will always get the latest API documentation of their project. Additionally phpUnderControl extracts the documentation violations found by the PhpDocumentor and visualizes these as an additional quality report in the user interface and the project time line of documentation violations.   * Documentation: PhpDocumentor, to generate an up to date documentation of the software on every build cycle. Therefore the developers will always get the latest API documentation of their project. Additionally phpUnderControl extracts the documentation violations found by the PhpDocumentor and visualizes these as an additional quality report in the user interface and the project time line of documentation violations.
Ligne 188: Ligne 198:
  
 ==== SimpleTest ==== ==== SimpleTest ====
 +<WRAP center round important 60%>
 +SimpleTest c'est fini.
 +</WRAP>
  
-http://www.simpletest.org+<del>http://www.simpletest.org</del>
  
 It is a PHP unit test and web test framework. Users of JUnit will be familiar with most of the interface. The JWebUnit style functionality is more complete now. It has support for SSL, forms, frames, proxies and basic authentication. The idea is that common but fiddly PHP tasks, such as logging into a site, can be tested easily.  It is a PHP unit test and web test framework. Users of JUnit will be familiar with most of the interface. The JWebUnit style functionality is more complete now. It has support for SSL, forms, frames, proxies and basic authentication. The idea is that common but fiddly PHP tasks, such as logging into a site, can be tested easily. 
Ligne 236: Ligne 249:
  
 PHP_CodeSniffer tokenizes PHP files and detects violations of a defined set of coding standards.  PHP_CodeSniffer tokenizes PHP files and detects violations of a defined set of coding standards. 
 +
 +PHP_CodeSniffer is a set of two PHP scripts:
 +
 +  * the main ''phpcs'' script that tokenizes PHP files to detect violations of a defined coding standard ;
 +  * and ''phpcbf'' script to automatically correct detected coding standard violations.
  
 ===== Librairies ===== ===== Librairies =====
informatique/php.1784008554.txt.gz · Dernière modification : de cyrille
Sauf mention contraire, le contenu de ce wiki est placé sous les termes de la licence suivante : CC0 1.0 Universal
CC0 1.0 Universal Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki