Getting (remote) debugging setup for web-based applications can be a finicky and intricate affair at times, depending on the structure of your development environment. This article doesn’t cover debugging web-based applications with PhpStorm, but smaller code libraries. So that’s why, in this article, I’m going to show you how to integrate Xdebug, PHPUnit, and PhpStorm. Whenever I write PHP code, it’s reasonably safe to say that I use PhpStorm. Gladly, to set it up in PHP, you don’t need a lot. If you’re not familiar with step-through debugging, it’s where you, as the name implies, step through your code, one line at a time. The solution was to use use step-through debugging in PhpStorm. I needed to know what was being returned, but the ham-fisted way I was attempting to find it wasn’t working. Not only did I not see the value that I wanted, I saw an unwieldy stack trace instead. Well, if you’ve ever tried to var_dump a variable in the middle of a PHPUnit test, then you’ll know that PHPUnit doesn’t take kindly to that. Instinctively ( wrongly) I started using PHP’s var_dump method to attempt to see what the value being returned was. However, in others, the values that I expected to be returned, weren’t. In the early stages of development, in some cases, the tests validated that the expected values were being returned. Have a look at the project’s tests for a full list, but here’s a short list. Not such a tricky request, you might think.īut the more test data I fed the code, the more use cases I found which needed to be handled. Its task is to filter a European-format currency string, such as -1.432.156,54 into its integer equivalent. One example is a package called currency-filter. These dependent packages perform several smaller tasks, ones that don’t belong in the main package. Recently, I’ve been developing a side-project, and have had to create several dependent packages to support it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |