Recherche avancée

Sur d’autres sites (4032)

• Anomalie #3861 : Tri et caractères accentués dans boucle DATA

  23 février 2020, par Maïeul Rouquette

  Je reviens sur ce problème. Si on utilise la fonction sort de php, il est possible de préciser par une constante qu’on veut utiliser un tri suivant la chaine de langue locale ( SORT_LOCALE_STRING). Ne serait-ce pas envisageable de s’en servir ?

  https://www.php.net/manual/fr/function.sort.php

• lavf : Use wchar functions for filenames on windows for mkdir/rmdir/rename/unlink

  17 novembre 2014, par Martin Storsjö

  lavf : Use wchar functions for filenames on windows for mkdir/rmdir/rename/unlink
  This makes sure that the internal utf8 path names are handled
  
  properly - the normal file handling functions assume path names
  
  are in the native codepage, which isn’t utf8.
  This assumes that the tools outside of lavf don’t use the mkdir
  
  definition. (The tools don’t do the same reading of command line
  
  parameters as wchar either - they probably won’t handle all possible
  
  unicode file parameters properly, but at least work more predictably
  
  if no utf8/wchar conversion is involved.)
  This is moved further down in os_support.h, since windows.h shouldn’t
  
  be included before winsock2.h, while io.h needs to be included before
  
  the manual defines for lseek functions.
  Signed-off-by : Martin Storsjö <martin@martin.st>
  

  • [DBH] libavformat/internal.h
  • [DBH] libavformat/os_support.h

• How to write unit tests for your plugin – Introducing the Piwik Platform

  17 novembre 2014, par Thomas Steur — Development

  This is the next post of our blog series where we introduce the capabilities of the Piwik platform (our previous post was How to verify user permissions). This time you’ll learn how to write unit tests in Piwik. For this tutorial you will need to have basic knowledge of PHP, PHPUnit and the Piwik platform.

  When is a test a unit test ?

  There are many different opinions on this and it can be sometimes hard to decide. At Piwik we consider a test as a unit test if only a single method or class is being tested and if a test does not have a dependency to the filesystem, web, config, database or to any other plugin.

  If a test is slow it can be an indicator that it is not a unit test. “Slow” is of course a bit vague. We will cover how to write other type of tests, such as integration tests, in one of our next blog posts.

  Getting started

  In this post, we assume that you have already installed Piwik 2.9.0 or later via git, set up your development environment and created a plugin. If not, visit the Piwik Developer Zone where you’ll find the tutorial Setting up Piwik and other Guides that help you to develop a plugin.

  Let’s create a unit test

  We start by using the Piwik Console to create a new unit test :

  ./console generate:test --testtype unit

  The command will ask you to enter the name of the plugin the created test should belong to. I will use the plugin name “Insights”. Next it will ask you for the name of the test. Here you usually enter the name of the class you want to test. I will use “Widgets” in this example. There should now be a file plugins/Insights/tests/Unit/WidgetsTest.php which contains already an example to get you started easily :

  /**
   * @group Insights
   * @group WidgetsTest
   * @group Plugins
   */
  class WidgetsTest extends \PHPUnit_Framework_TestCase
  {
   
      public function testSimpleAddition()
      {
          $this->assertEquals(2, 1+1);
      }
   
  }
  Télécharger

  We don’t want to cover how you should write your unit test. This is totally up to you. If you have no experience in writing unit tests yet, we recommend to read articles on the topic, or a book, or to watch videos or anything else that will help you learn best.

  Running a test

  To run a test we will use the command tests:run which allows you to execute a test suite, a specific file or a group of tests.

  To verify whether the created test works we will run it as follows :

  ./console tests:run WidgetsTest

  This will run all tests having the group WidgetsTest. As other tests can use the same group you might want to pass the path to your test file instead :

  ./console tests:run plugins/Insights/tests/Unit/Widgets.php

  If you want to run all tests within your plugin pass the name of your plugin as an argument :

  ./console tests:run insights

  Of course you can also define multiple arguments :

  ./console tests:run insights WidgetsTest

  This will execute all tests within the insights plugin having the group WidgetsTest. If you only want to run unit tests within your plugin you can do the following :

  ./console tests:run insights unit

  Advanced features

  Isn’t it easy to create a unit test ? We never even created a file ! You can accomplish even more if you want : You can generate other type of tests, you can run tests on Amazon’s AWS and more. Unfortunately, not everything is documented yet so we recommend to discover more features by executing the commands ./console list tests and ./console help tests:run.

  If you have any feedback regarding our APIs or our guides in the Developer Zone feel free to send it to us.