Fix wrong order of applied arguments

Since when 3.3.0 all node functions mix up the order of arguments when the number of supplied arguments is exactly 2 (which has probably been introduced with b4d00971391d564c9899b98e3ff5068c24b1a68f).

This pull-request fixes this problem and improves the tests to check for the correct order of arguments as well.