Jump to content

Search the Community

Showing results for tags 'phpunit'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Welcome to PHP Freaks
    • Announcements
    • Introductions
  • PHP Coding
    • PHP Coding Help
    • Regex Help
    • Third Party Scripts
    • FAQ/Code Snippet Repository
  • SQL / Database
    • MySQL Help
    • PostgreSQL
    • Microsoft SQL - MSSQL
    • Other RDBMS and SQL dialects
  • Client Side
    • HTML Help
    • CSS Help
    • Javascript Help
    • Other
  • Applications and Frameworks
    • Applications
    • Frameworks
    • Other Libraries
  • Web Server Administration
    • PHP Installation and Configuration
    • Linux
    • Apache HTTP Server
    • Microsoft IIS
    • Other Web Server Software
  • Other
    • Application Design
    • Other Programming Languages
    • Editor Help (PhpStorm, VS Code, etc)
    • Website Critique
    • Beta Test Your Stuff!
  • Freelance, Contracts, Employment, etc.
    • Services Offered
    • Job Offerings
  • General Discussion
    • PHPFreaks.com Website Feedback
    • Miscellaneous

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL








Donation Link

Found 4 results

  1. I am refactoring legacy code. I have a function called "load" that inside had a messy function called "loadProduct". I refactored "loadProduct" to look nice and clean (with some exception code put in place, and now code looks something like this: Design { function load() { loadProduct(); ... //lots of other stuff, legacy code, etc. etc. } function loadProduct() { try { //these two line below replaced what used to be about 30 lines of legacy code with SQL and DB specific code //those lines are now inside Product()->loadSpecs() method $this->product = new Product(); $this->product->spec = $this->product->loadSpecs($this->a, $this->b, $this->input->c); } catch (\BadFunctionCallException $e) { $this->error = true; $this->emsg = $e->getMessage(); } } } Now, here is my "big" problem and a list of questions that I do not know how to figure out best: Before I refactored, I wrote some fairly extensive Unit Tests for loadProduct() function. My tests verify various paths, like when the product is Loaded, when it is not loaded, and ALSO they verify that parameters inside that catch block above are set accordingly - that is they exercise the entire loadProduct() function as-is. But here is what I want to do next: I want to take the code inside of function called "loadProduct()", and move it into function "load". Note that existing code (indicated by dots ...) inside the "load" function will stay in place and hence be after the code I will move there. Then, since "loadProduct" function will be empty, I can remove it entirely. Of course this will mean that: My tests will no longer run (I removed the function tests were testing!) Well, that is a bummer! What I can do perhaps is I can modify my tests to instead of testing the old function code ["loadProduct()"], to test the the new class ["Product()"]and its method ["loadSpecs()"] that I have created. Note that if I do so, I will no longer be able to test the parameters being set outside of the Product class. So even after doing work to repurpose my tests to the Product() class, I will lose parts of my tests that verified things like parameters inside the catch block above, because those did not make it into the new Product() class. So what to do? Do I just leave the code as is as I printed above and "be happy" with that my tests work and that my loadMotor() function is being thoroughly tested? The reason that I wanted to move the loading code out of "loadProduct()" in the first place is/was a part of my refactoring effort. You see ... loadProduct() had SQL code inside of it, and loadProduct() was part of a bigger class [called Design()] that does NOT deal with SQL or DB-functionality. So I moved the DB-SQL-functionality into a DAO pattern class which I called Product(). So I figured if I can move DB-loading part into a separate class, maybe I can remove the function that did the loading as I now have a class I can call instead of it as part of the more general "load" function. I may be wrong. I can also do what's described in #3 - leave code as-is, but now repurpose my tests to tests "load()" function instead. This means repurposing tests to add whatever else load() function does. I don't think it is a good solution as load() does a lot of stuff (as indicated by dots ...) in my original code above. There is all kinds of legacy code in there that I did not yet wrap my mind about, nor wrote tests fo..... So I come to you, the resident forum folks, to maybe guide me with your wisdom Much thanks for reading all this of course! What path, if any I shall take in my legacy code refactoring efforts?
  2. I want to write a test for a complex legacy code function called load(); It loads various products from different product lines, so it can have many different actual parameters and number of parameters being used by it. It has an if/then/else/if else/if else/etc. inside of it, and depending on the product, it uses almost completely different product logic. I can call testLoad() inside of my PHPUnit test, but which product do I test? well, maybe I can do testLoadProduct1(), testLoadProduct2(), testLoadProduct3(), etc. Is that the recommended way to do it, or is there better way? In a sense I need to call the same method with vastly different parameters, and the test object will be producing vastly different results every time. I figure that with the way I proposed, if anything breaks, it will be immediately clear which methods (products) actually failed the tests, which should give me a clear idea what needs to be fixed or changed. So maybe my approach is the best. Still, just starting out with phpunit, I wanted to ask here to double-check. Thanks!
  3. I have some long block of code //features.php elseif ($feature=="X") { //...utter mess to be refactored.. if ($motor>0) { $a = getFeature($motor, $featureSpec); $b = getFlightInfo($motor, $flightNumber); $c = getWeather($motor); } } elseif ($feature=="Y") { // ...utter mess to be refactored.. } elseif ($feature=="Y") { // ...utter mess to be refactored.. } It is difficult to trace, but I can find out if features.php is included into some other files, and who calls it. In fact this may be a tangled mess, but that being said, do I need to know all the details, or can I stick PHPUnit on a certain blocks of code and just run with it? Like, say I want to test the if ($motor>0) block. Can I do this, without knowing anything else, like where is features.php included, and so on? If so, how do I test this? How do I inject PHPUnit's test into normal code execution?
  4. I have managed to get PHPUnit to work with NetBeans, but I'm experiencing a problem when I go to create a test of the back of a class as described in the documents https://netbeans.org/kb/docs/php/phpunit.html It throws out an error in the output area, PHPUnit Skeleton Generator 1.2.1 by Sebastian Bergmann. Warning: require_once(..\..\file.php): failed to open stream: No such file or directory in C:\Server\www\myserver.dev\public_html\site\Classes\subFolder\class.php on line 5 Fatal error: require_once(): Failed opening required '.\.\constants.php' (include_path='.;C:\Server\PHP\pear') in C:\Server\www\myserver.dev\public_html\site\Classes\subFolder\class.php on line 5 When I look at a page that is calling the class and put a die within file.php, say "test" I see the output. So i'm not entirely sure what is going on, anyone got any ideas? Just to note I'm running a WAMP environment rather than a LAMP.
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.