Unittests

XP Compiler on Travis

On a short note: Just like any part of XP Technologies, the XP Language and its compiler are unittested. And since today, these tests are also run on Travis-CI.

RFC #0267: Unittest parameterization

Scope of Change
This will extend the unittest API by adding a facility for providing values to a test.

Rationale
This will make it easier to discover problems in tests written using foreach loops currently, and at the same time reduce the amount of code that needs to be written for tests with separate test methods for every value.

Read the full RFC here.

Ubuntu users: Heads up!

If you recently updated your runners using the xprt-update.sh script distributed alongside them, you would start receiving errors such as

  ./unittest: 99: ./unittest: Bad substitution

  $ cd /path/to/xp/runners
  $ wget http://releases.xp-framework.net/setup/bin -O - | php

5.8.6-RELEASE: Unittests

The XP Group is proud to announce the immediate availability of the XP Framework release 5.8.6. This release has focussed on improving the unittests APIs:

• We have improved unittest's error messages as described in RFC #0256 as well as for large strings
  
• Tests can now be skipped from within themselves by calling $this->skip($reason)
  
• Multiple @beforeClass / @afterClass methods are now allowed - see RFC #0255.
  
• Unittest output is colored if a capable terminal window is detected
  
• The unittest command line runner now accepts file system paths in its argument list and will run all tests inside it
  

  $ cd ~/xp
  $ wget http://releases.xp-framework.net/setup/5.8.6 -O - | php -- -d ~/bin/

Enjoy

Surpassed 5000 unittests

On a short note: The XP Framework's core now surpassed 5000 unittests:

  $ unittest src/test/resources/*ini
  [...]
  OK: 5177/5450 run (273 skipped), 5177 succeeded, 0 failed
  Memory used: 42736.45 kB (50112.08 kB peak)
  Time taken: 14.374 seconds

"Infinitest" with the XP Framework

Thinking about our upcoming 5.8.6 release whose focus is on unittesting, I recently came up with the idea to have unittests run whenever I change, and save, the code I'm working on (yesterday evening I found out in the Java world this is called "infinitest" - my focus though was to get this done on the command line, without the necessity to plug in to various IDEs).

Searching for utilities to monitor the file system for changes, I found the "inotify tools". Since I work on Windows using Cygwin though, I decided to "port" them using the .NET Framework's FileSystemWatcher class. The results can be found here (just clone and run "make" - prerequisites are .NET Framework v3.5).

Given this, the basic command line is:

  $ inotifywait -r -m src/ | while read line ; do \
      # The action to be executed when files are modified inside the "src" 
      # directory or any of its subdirectories
    done

infinittest for XP running in a mintty window

  $ inotifywait -r -m src/ | while read line ; do \
      unittest -l xp.unittest.XtermTitleListener - src/ ; \
    done

RFC #0255: Allow multiple @beforeClass / @afterClass methods

Scope of Change
The unittest runner will support running multiple @beforeClass / @afterClass methods.

Rationale
Greater flexibility

Read the full RFC here

Continuous integration in the cloud

Thanks to Alex we're now integrated with Travis CI!

To learn more about Travis CI, visit their about page.

5.8.4-RELEASE: Multiple config sources, selectable database drivers, SQLite3, MySQL local sockets, mocking library

The XP group is proud to announce the immediate availability of framework release 5.8.4. After four release candidates and about three and a half months, we deliver a bigger release, including the following:

Multiple config sources
This feature described in RFC #0221 enables combining properties from more than one source (e.g., ini-files). For example, one can now have a global, system-wide configuration and extend on that in your application. This feature is supported by "XPCLI" commands and the web runner - details can be found here.

Selectable database drivers
With more and more database protocols appearing as userland implementation (MySQL, Sybase, MSSQL), the urge to be able to chose between drivers has come up; and be it just for testing. To select a specific driver, append the implementation name to the driver, e.g. mysql+std to select ext/mysql. To retrieve the default MySQL driver, one can still use mysql://user@host DSN syntax.

SQLite3
With the deprecation of SQLIte2 in PHP 5.4, we have decided to implement SQLIte3 support in the XP Framework. At the same time, and because we now offer selectable drivers, the default is SQLIte3.

MySQL local sockets
We now support local socket connectivity in our MySQL driver implementation by using the special hostname ".": By using "mysql://./DATABASE", we connect through a local socket, while "mysql://localhost/DATABASE" uses TCP/IP. This has been unified throughout the various MySQL drivers.

Mocking library
The package unittest.mock contains the all-new mocking library. The API is modeled in a fashion similar to EasyMock (Java), Rhino Mocks (.Net). You can read all about the details in RFC #219.

...and more
We have almost 20 bugfixes and various features included in this release - all of which can be seen in the ChangeLog.

  $ cd ~/xp
  $ wget http://releases.xp-framework.net/setup/5.8.4 -O - | php -- -d ~/bin/

Enjoy

Overwriting Testcase's special methods

A fix has been committed to the unittest API that prevents (accidentally) overwriting special methods from unittest.TestCase. What had happened is the following:

  class SystemPropertyTest extends TestCase {
    
    #[@test]
    public function getName() {
      $this->assertEquals('...', $this->fixture->getName());
    }
  }

Subscribe

You can subscribe to the XP framework's news by using RSS syndication.

Categories