TS 70 PHP Sanity

PHP Sanity Test Specification for NetBeans 7.0

Author: Maghiel Dijksman, updates by Vladimir Riha
Original author: Filip Zamboj [TS_69_PHP_Sanity]
Last update: 16th April 2012
Introduction: Sanity specification for NetBeans PHP
Comments: Sanity

Contents


Test suite: Create a new Php Project

Purpose: Check the Wizard for creation empty Php Project.
Setup: PHP engine and Apache HTTP Server are configured. Apache is installed to default location. Symfony and Zend frameworks are installed and configured. It's assumed that Symfony and Zend framworks are on path during testing. It's tester's responsibility to successfully install and setup 3rd party software.
Recommendation: install Symfony using pear.

  1. Create an empty Project with default settings.
    1. In the Projects window, choose File > New Project.
    2. In the Categories list, select PHP. In the Projects area, choose PHP Application to create an empty project and click Next.
    3. Accept default values for Name and Location step. Press Finish button.
    • EXPECTED RESULT: Created Php project appears on Project tab. index.php opens in the source view. Project Sources are located in htdocs directory of Apache.
  2. Create empty Project with the given name
    1. In the Projects window, choose File > New Project.
    2. In the Categories list, select PHP, in the Projects area, choose PHP Application to create an empty project and click Next.
    3. Type Project Name myPhpProject. the rest fields use default values for Name and Location step, press Finish button.
    4. Repeat above steps for creating project with the same name.
    • EXPECTED RESULT: There should be the warning message: Source directory is already NetBeans project.
  3. Create empty Project with incorrect name
    1. In the Projects window, choose File > New Project.
    2. In the Categories list, select PHP, in the Projects area, choose PHP Application to create an empty project and click Next.
    3. For Name and Location step type Project Name myPhpProject*. Accept default values for the rest fields, press Cancel button.
    • EXPECTED RESULT: There should be warning message: Source directory is not a valid folder name.
  4. Create empty Project and put metadata into a separate directory
    1. In the Projects window, choose File > New Project.
    2. In the Categories list, select PHP, in the Projects area, choose PHP Application to create an empty project and click Next.
    3. Check "Put NetBeans metadata into a separate directory" checkbox. Accept default values for the rest fields, press Finish button.
    • EXPECTED RESULT: Created Php project appears on Project tab. Index.php opens in source view. Project Sources are located in the Source Folder and metadata are located in a separate directory.
  5. Create empty Project with renamed index.php file
    1. In the Projects window, choose File > New Project.
    2. In the Categories list, select PHP, in the Projects area, choose PHP Application to create an empty project and click Next.
    3. Accept default values for the rest fields, press Finish button.
    4. Rename index.php Index File to myindex.php.
    5. Invoke Properties for this PHP Application. Slect Run Configuration on Properties window. Press "Browse..." button for index file. Select myondex.php file. Press Select File button. Press OK.
    • EXPECTED RESULT: Created Php project appears on Project tab. Index file has new name myindex.php opens
  6. Create empty Project and choose copy location.
    1. In the Projects window, choose File > New Project.
    2. In the Categories list, select PHP, in the Projects area, choose PHP Application to create an empty project and click Next.
    3. Accept default values for the rest fields, press Next button.
    4. Set checkbox 'Copy files from Sources Folder to another location' on. Press Browse button and select path for copying. Press Finish button.
    • EXPECTED RESULT: Created Php project appears on Project tab. index.php opens in source view. Project Sources are located in the Sources Folder and have a copy in Copy Location without netbeans specific files located in nbproject directory.
  7. Create Symfony project
    1. In the Projects window, choose File > New Project.
    2. In the Categories list, select PHP, in the Projects area, choose PHP Application to create an empty project and click Next.
    3. Accept default values for the rest fields, press Next button.
    4. In last step check Symfony PHP Web Framework
    5. Press Finish button
    • EXPECTED RESULT: Created Php project appears on Project tab with framework specific icon.
  8. Create Zend project
    1. In Projects window, choose File > New Project.
    2. In Categories list, select PHP, in the Projects area, choose PHP Application to create an empty project and click Next.
    3. Accept default values for the rest fields, press Next button.
    4. In last step check Zend PHP Web Framework
    5. Press Finish button
    • EXPECTED RESULT: Created Php project appears on Project tab with framework specific icon.
  1. Framework enhancements.
    1. In the main menu, choose File > New Project... And create new php project with Zend Framework.
    • EXPECTED RESULT: The project should have a similiar file structure with the same icons used as on the picture below, files has different icons depending on their purpose.

File:Php-improvements.png


Test suite: Create Sample Application

Purpose: Create the sample and work with it.
Setup: PHP engine, Apache 2.2 and MySQL data base are configured. Apache 2.2 is installed to default location.

  1. Create TodoList Sample
    1. In the Projects window, choose File > New Project.
    2. In the Categories list, select Samples>PHP. In the Projects area. Choose TodoList Sample Application to create the sample. Press Next.
    3. Name of Project is TodoListN where N is used when Project with the same name already exists in default project folder and N > 0.
    4. Press Finish.
    5. Folow the instruction in the appeared readme.html.
    • EXPECTED RESULT: Created TodoList Sample appears on Project tab. There should be opened readme.html in default browser.

Test suite: Check Properties of PHP Project

Purpose: Check Properties of PHP Project
Setup: PHP engine, Apache HTTP server and MySQL data base are configured.

  1. Check Properties of php Project with default settings.
    1. In the Projects window, choose File > New Project.
    2. In the Categories list, select PHP. In the Projects area, choose PHP Project to create an empty project and click Next.
    3. Accept default values for Name and Location step, press Finish button.
    4. Created Php project appears on Project tab. Right click on the project and select Properties.
    • EXPECTED RESULT: Project Properties window appears. There are six Categories: Sources, Run Configuration, PHP Include Path, Ignored Folders, PHPUnit, PhpDoc, Formatting.


Test suite: Run file without project

Purpose: Check that you can run and debug file without project
Prerequisites: some PHP file

  1. Test running file without project .
    1. In the main menu, choose File > Open File... And open your php file
    2. Right click in the file content (text editor), then Run File (SHIFT + F6)
    • EXPECTED RESULT: Similiar dialog as on the picture below appears and the file has correct output - you can see the output in Output Window

File:Run-file-1.png


Test suite: Debug file without project

  1. Test debugging file without project .
    1. In the main menu, choose File > Open File... And open your php file
    2. Right click in the file content (text editor), then Debug File (CTRL + SHIFT + F5)
    • EXPECTED RESULT: Similiar dialog as on the picture below appears.

File:Run-file-2.png


Test suite: Code Completion

Purpose: Check that code completion works properly in PHP code and HTML for PHP source and PHP web page.
Prerequisites: a PHP project is created in the Netbeans IDE.

  1. Create a PHP source file.
    1. In the main menu, choose File > New File...
    2. In the Categories list, select PHP. In the File Types list, choose PHP File. Click Next.
    3. Accept default values by pressing Finish button.
    • EXPECTED RESULT: A new PHP file is created and opened in the editor.
  2. Verify automatic code completion invocation.
    1. In PHP source, type $.
    • EXPECTED RESULT: Code completion is invoked automatically - a list of available variables appears.
  3. Verify local variable code completion.
    1. Create a PHP function.
    2. Declare a variable in the function.
    3. Type several first symbols of the variable name and invoke code completion.
    • EXPECTED RESULT: Code completion appears and the variable name is among suggestions.
  4. Verify global variable code completion.
    1. Create a PHP function.
    2. Declare a global variable.
    3. Type several first symbols of the variable name and invoke code completion.
    • EXPECTED RESULT: Code completion appears and the variable name is among suggestions.
  5. Verify variable from included file code completion.
    1. Include an other PHP file into PHP source.
    2. Open that PHP source and create a global variable there.
    3. Create a PHP function in the first source.
    4. Inside that function, type the global keyword followed by several first symbols of the variable name and invoke code completion.
    5. Choose that variable in the list and press Enter.
    • EXPECTED RESULT: Code is completed properly. No require or include directive is auto-generated.
  6. Verify variable from required file code completion.
    1. Add an other PHP file into PHP source using the require directive.
    2. Open that PHP source and create a global variable there.
    3. Create a PHP function in the first source.
    4. Inside that function, type several first symbols of the variable name and invoke code completion.
    5. Choose that variable in the list and press Enter.
    • EXPECTED RESULT: Code is completed properly. No require or include directive is auto-generated.
  7. Verify code completion inside the identifier.
    1. Place the caret inside of existing PHP identifier.
    2. Invoke code completion.
    • EXPECTED RESULT: Code completion appears and the list of suggestions corresponds to the beginning of the identifier.
  8. Verify documentation hints for built-in identifiers.
    1. see #199261 first
    2. Invoke code completion for a whitespace.
    3. Select a built-in identifier in the list (like $GLOBALS, $_ENV)
    • EXPECTED RESULT: In the details code completion view, a description of the identifier appears.
  9. Verify documentation hints for keywords.
    1. Check #199406
    2. Invoke code completion for a whitespace.
    3. Select a keyword in the list (like extends, if).
    • EXPECTED RESULT: In the details code completion view, a description of the keyword appears.
  10. Verify keywords code completion.
    1. Type the beginning of a keyword in a situation appropriate for its usage.
    2. Invoke code completion.
    • EXPECTED RESULT: Code completion appears and the keyword is among suggestions.
  11. Verify code completion with a single option.
    1. Type the beginning of a identifier so that there is only one option for code completion.
    2. Invoke code completion.
    • EXPECTED RESULT: Identifier is instantly completed without any popup windows.
  12. Verify JavaDoc window.
    1. Create a PHP function.
    2. Add some JavaDoc to that function. Don't save the source.
    3. In some other place, type the beginning of that function name and invoke code completion.
    4. Select that function in the popup window.
    • EXPECTED RESULT: Just entered JavaDoc is shown in the JavaDoc window of code completion.
  13. Verify code completion after EXTENDS.
    1. Define Foo class.
    2. Type "class MyClass extends F".
    3. Invoke code completion.
    • EXPECTED RESULT: Code completion appears and Foo class is shown. No any other identifiers are shown besides build-in PHP classes and extension.
  14. Verify code completion in // comments.
    1. Create // style comment .
    2. Invoke code completion at that line after //.
    • EXPECTED RESULT: Code completion doesn't appear. It shouldn't be available in comments.
  15. Verify code completion in /* */ comments.
    1. Create /* */ style comment .
    2. Invoke code completion inside of that comment.
    • EXPECTED RESULT: Code completion appears. Originally, the expected result was "doesn't appear", but since it does and it's probably useful let's change the expected result to "does appear".
  16. Verify code completion in /** */ comments.
    1. Create /** */ comment .
    2. Type "@" and invoke code completion.
    • EXPECTED RESULT: Code completion shows a list of JavaDoc tags (like @abstract).
  17. Verify smart method code completion
    1. Copy the code below to php file
    2. Invoke code completion at place of "|" (first remove the "|" char from code)
    • EXPECTED RESULT: Code completion the bar method, when you confirm it following is inserted bar($string, $int, $float), so the parameters are filled in based on their types and type described in PhpDoc of function bar() .
class Foo{   
    /**
     *Some PhpDoc
     * @param string $s
     * @param int $i
     * @param float $f 
     */
    function bar($s, $i, $f){}
    
    function foobar(){
        $string ="";
        $int = 42;
        $float = 3.1456;
        $this->|       
    }
}
  1. Verify smart try/catch code completion
    1. Use the code belos
    2. Invoke code completion at place of "|" (first remove the "|" char from code)
    • EXPECTED RESULT: Code completion offers only classes inherited from Execption.
   try{
      new AppendIterator;
    }  catch (|)
    }


Test suite: Code Folding

Purpose: Check that PHP code and HTML is folded properly for PHP source and PHP web page.
Prerequisites: a PHP project is created in the Netbeans IDE.

  1. Create a PHP web page.
    1. In the main menu, choose File > New File...
    2. In the Categories list, select PHP. In the File Types list, choose PHP Web Page. Click Next.
    3. Accept default values by pressing Finish button.
    • EXPECTED RESULT: A new PHP web page is created and opened in the editor.
  2. Verify code fold tooltip.
    1. Collapse a code fold.
    2. Move mouse cursor onto {...} folding symbols.
    • EXPECTED RESULT: Full content of folded code should appear as a tooltip.
  3. Expand code fold by double-click.
    1. Collapse a code fold.
    2. Double-click {...} folding symbols.
    • EXPECTED RESULT: Code fold is expanded.
  4. Recurrent code folding.
    1. Collapse several code folds.
    2. Collapse a code fold containing all of them.
    3. Expand that code fold back.
    4. Expand all other code folds.
    5. Collapse that main code fold again.
    6. Expand that code fold back.
    • EXPECTED RESULT: When expanding the main code fold back, other code fold should be in the same states as they were before collapsing the main code fold.
  5. Repeat all previous testcases for HTML folding.
    • EXPECTED RESULT: Same as in previous testcases.
  6. PHP functions code folding.
    1. Add a PHP code with function definition to the page.
    2. Collapse a code fold with this function.
    3. Expand that code fold back.
    • EXPECTED RESULT: The code fold should exist and work properly. The function title should be displayed outside of code fold.
  7. PHP /**/ comments code folding.
    1. Add a PHP code with /**/ style comment to the page.
    2. Collapse a code fold with this comment.
    3. Expand that code fold back.
    • EXPECTED RESULT: The code fold should exist and work properly.
  8. PHP // comments code folding.
    1. Add a PHP code with several lines of // style comments to the page.
    • EXPECTED RESULT: No code fold should exist for that comments.
  9. Copy/Paste code folds.
    1. Add a PHP function with the body.
    2. Collapse its fold.
    3. Copy the fold (mark it and press Ctrl-C).
    4. Paste code in some other place.
    • EXPECTED RESULT: Code is pasted properly and is unfolded.
  10. Verify code folding from the main menu.
    1. In the IDE main menu, choose View -> Code Folds.
    2. Try each item of this submenu: Collapse Fold, Expand Fold, Collapse All, Expand All.
    • EXPECTED RESULT: Code folds behave correspondingly.
  11. Verify code folding via keyboard shortcuts. Note: Keyboard shortcuts are currently not displayed next to the menu items. This is a know issue: Bug 180985 - Code folding menu items should list primary shortcuts
    1. In the IDE main menu, choose View -> Code Folds.
    2. Behold keyboard shortcuts for each item of this submenu. (See note above)
    3. Keyboard shortcuts are: Collapse All: ctrl+shift+substract / ctrl+shift+minus. Collapse Fold: ctrl+minus / ctrl+substract. Expand All: ctrl+shfit+[add|equals|plus]. Expand Fold: ctrl+[plus|add|equals]
    4. Press shortcut for each item of this submenu: Collapse Fold, Expand Fold, Collapse All, Expand All.
    • EXPECTED RESULT: Code folds behave correspondingly.


Test suite: Mark Occurrences

Purpose: Check that occurrences of PHP identifier highlighted when of the identifiers is selected.
Prerequisites: a PHP project is created in the Netbeans IDE.

  1. Create a PHP web page.
    1. In the main menu, choose File > New File...
    2. In the Categories list, select PHP. In the File Types list, choose PHP Web Page. Click Next.
    3. Accept default values by pressing Finish button.
    4. Copy/paste a large PHP code peace into the editor.
    • EXPECTED RESULT: A new PHP web page is created and opened in the editor. The code is added there.
  2. Verify local variable occurrences marking.
    1. Create several PHP functions.
    2. Introduce a global variable.
    3. Introduce a variable with the same name in each of these functions.
    4. Add operators which use each of these variables.
    5. Place the cursor onto usage one of these variables.
    • EXPECTED RESULT: Definition and usages of this variable are highlighted. Definition and usages of other variables aren't.
  3. Verify function occurrences marking.
    1. Create a PHP function.
    2. Add several calls of that function, both inside and outside of its code.
    3. Place the cursor onto one of these calls.
    • EXPECTED RESULT: Definition and calls of this function are highlighted.
  4. Verify parameter occurrences marking.
    1. Create a PHP function with a parameter.
    2. Use that parameter in the function body.
    3. Place the cursor onto one of these usages.
    • EXPECTED RESULT: Definition and usages of this parameter are highlighted.
   <?php
        // put your code here
        $bar = 1;

        function foo($bar) {
            $bar = 2;
        }

        function foo2() {
            $bar = 1;
        }

        function foo3() {
            global $bar;
            $bar = 2;
        }
        ?><div></div>
        <?php foo3(); ?>




Test suite: HTML Palette

Purpose: Check adding the HTML Palette components to PHP source.
Prerequisites: a PHP project is created in the Netbeans IDE.

  1. Create a PHP web page.
    1. In the main menu, choose File > New File...
    2. In the Categories list, select PHP. In the File Types list, choose PHP Web Page. Click Next.
    3. Accept default values by pressing Finish button.
    • EXPECTED RESULT: A new PHP web page is created and opened in the editor. A button to open the palette window is shown on the right, depending on the user's preferences.
  2. DnD Table HTML component to HTML code.
    1. DnD Table HTML component to the editor, not into PHP code.
    2. In the "Insert Table" dialog, press OK.
    • EXPECTED RESULT: HTML tags added to DnD position. They correspond to visual representation of Table HTML component in the "Insert Table" dialog.
  3. DnD Table HTML component to PHP code.
    1. DnD Table HTML component to the editor, into PHP code.
    2. In the "Insert Table" dialog, press OK.
    • EXPECTED RESULT: HTML tags added to DnD position. They correspond to visual representation of Table HTML component in the "Insert Table" dialog. Editor lines are marked with red, and tooltip reads "Syntax error".
  4. DnD big Table HTML component to HTML code. See Bug 196669
    1. DnD Table HTML component to the editor.
    2. In the "Insert Table" dialog, specify large values for rows and columns (like 1000), change values of other fields and press OK.
    • EXPECTED RESULT: After reasonable time (few seconds), HTML tags added to DnD position. They correspond to the visual representation of Table HTML component in the "Insert Table" dialog (with made changes).
  5. DnD Table HTML component with given parameters to HTML code.
    1. DnD Table HTML component to the editor.
    2. In the "Insert Table" dialog, change values of each field and press OK.
    • EXPECTED RESULT: HTML tags added to DnD position. They correspond to the visual representation of Table HTML component in the "Insert Table" dialog (with made changes).
  6. Add Table HTML component with given parameters to HTML code using double-click.
    1. Place the cursor to some position in editor.
    2. Double-click Table HTML component.
    3. In the "Insert Table" dialog, change values of each field and press OK.
    • EXPECTED RESULT: HTML tags added to DnD position. They correspond to the visual representation of Table HTML component in the "Insert Table" dialog (with made changes).
  7. Undo adding Table HTML component to HTML code.
    1. DnD Table HTML component to the editor.
    2. In the "Insert Table" dialog, change values of each field and press OK.
    3. In the main menu, choose Edit -> Undo.
    • EXPECTED RESULT: HTML tags added to DnD position, but reverted after Undo.
  8. DnD Form HTML component with given parameters to HTML code.
    1. DnD Form HTML component to the editor.
    2. In "Insert Table" dialog, change values of each field and press OK.
    • EXPECTED RESULT: HTML tags added to DnD position. They correspond to the visual representation of Form HTML component in the "Insert Form" dialog (with made changes).
  9. DnD other HTML components with given parameters to HTML code.
    1. Same as previous, for other components in HTML Palette.
    • EXPECTED RESULT: HTML tags added to DnD position. They correspond to the visual representation of an HTML component in the insert dialog (with made changes).


Test suite: Formatting

Purpose: Check Format code feature for PHP and HTML.
Prerequisites: a PHP project is created in the Netbeans IDE.

  1. Create a PHP web page.
    1. In the main menu, choose File -> New File...
    2. In the Categories list, select PHP. In the File Types list, choose PHP Web Page. Click Next.
    3. Accept default values by pressing Finish button.
    • EXPECTED RESULT: A new PHP web page is created and opened in the editor.
  2. Format default code of PHP web page.
    1. Invoke Format from the popup menu in the editor.
    • EXPECTED RESULT: The page source isn't changed, since it's already formatted properly.
  3. Undo Formatting of PHP web page.
    1. Invoke Format from the popup menu in the editor.
    2. Choose Edit->Undo in the main menu.
    • EXPECTED RESULT: All formatting changes are reverted.
  4. Create a PHP file.
    1. In the main menu, choose File -> New File...
    2. In the Categories list, select PHP. In the File Types list, choose PHP File. Click Next.
    3. Accept default values by pressing Finish button.
    • EXPECTED RESULT: A new PHP file is created and opened in the editor.
  5. Format default code of PHP file.
    1. Invoke Format from the popup menu in the editor.
    • EXPECTED RESULT: The source isn't changed, since it's already formatted properly.
  6. Undo Formatting of PHP file.
    1. Invoke Format from the popup menu in the editor.
    2. Choose Edit->Undo in the main menu.
    • EXPECTED RESULT: All formatting changes are reverted.
  7. Formatting of folded code.
    1. Add code with code foldings, collapse several folds.
    2. Invoke Format from the popup menu in the editor.
    3. Expand those folds back.
    • EXPECTED RESULT: Folded code is formatted as well as unfolded.


Test suite: Navigation

Purpose: Check Navigation in PHP code.
Prerequisites: a PHP project is created in the Netbeans IDE.

TODO: Add test cases for the navigator and hierarchy type viewer

  1. Create a PHP web page.
    1. In the main menu, choose File -> New File...
    2. In the Categories list, select PHP. In the File Types list, choose PHP Web Page. Click Next.
    3. Accept default values by pressing Finish button.
    • EXPECTED RESULT: A new PHP web page is created and opened in the editor.
  2. Navigate to a specified line.
    1. In the editor popup menu, choose Navigation -> Line...
    2. Type a valid line number and press GoTo.
    • EXPECTED RESULT: The caret is moved to the specified line.
  3. Navigate to an invalid line.
    1. In the editor popup menu, choose Navigation -> Line...
    2. Type a line number which is greater that number of lines in the file and press GoTo.
    • EXPECTED RESULT: The caret is moved to the end of file.


Test suite: Type Hierarchy View

Purpose: Check that Type Hierarchy View works
Prerequisites: a PHP project is created in the Netbeans IDE.

  1. Type Hierarchy View
    1. Create new php file and declare a class called Foo.
    2. In the same file, declare new class called Bar that extends class Foo
    3. Invoke popup menu and select Navigate|Php Type Hierarchy
    4. New window called Php Type Hierarchy view is opened. It contains 2 classes and their relations to each other.

image:Hv.PNG

    1. Use the 2 buttons at the bottom to switch the view
    • EXPECTED RESULT: Subtype hierarchy displays class and its subclasses or interface and the classes that implement it. Supertype hierarchy displays classes that are extended and interfaces that are implemented .

Test suite: Aliases

Purpose: Check that aliases works in php file
Prerequisites: a PHP project is created in the Netbeans IDE.

  1. Aliases
    1. Create new php file and declare function called reallyLongNameForUselessFunction.
    2. In the lines below, type following:
use reallyLongNameForUselessFunction as shortName;
    1. Now, start typing shortN and invoke code completion. Whole name should be completed.
    • EXPECTED RESULT: Hold Ctrl and left click on calling of shortName, cursor should be moved to the line with reallyLongNameForUselessFunction declaration.

Test suite: Refactoring

Purpose: Check functioning of refactoring options offered for PHP projects
Preqequisites: New PHP project is created from NetBeans IDE

  1. Rename refactor a class method
    1. Create a class Foo with public methods bar($barStr) and baz.
    2. Add a method work to Foo, in which calls to bar and baz are made.
    3. Instantiate a new Foo object and add a call to bar() in index.php
    4. Go back to Foo.php, right click on method bar, and choose Refactor > Rename.
    5. In the dialog that appears enter netCat as "New name", and click Preview.
    6. Refactoring window appears showing diff of Foo.php and index.php before and after refactoring, finding 3 occurences. Click Do Refactoring.
    • EXPECTED RESULT: bar($barStr) is renamed to netCat($barStr). Foo::work() now calls netCat() instead of bar(). Method call in index.php is also renamed.
  2. Safely delete a class
    1. Use the project from the previous test case.
    2. Right click Foo.php and choose Delete.
    3. Tick "Safely delete (with usage search)" and click on Preview.
    • EXPECTED RESULT: NetBeans will give you a warning "References to elements in selected file were found. Remove all references to these elements in order to safely delete your file"
<?php

class FooBar {

    function bar($barStr) {
        
    }

    function baz() {
        
    }

    function work() {
        $this->bar(2);
        $this->baz();
    }

}

$bar = new FooBar();

$bar->work();
?>

Test suite: PHPDoc

Purpose: Check generation of documentation with PHPDoc
Prerequisites: PHPDoc installed and configured

  1. Generate documentation for a project
    1. Create a new PHP project.
    2. Create an interface FooInterface with some methods.
    3. Create an abstract class FooAbstract implementing FooInterface.
    4. Create a class Foo extending FooAbstract.
    5. Right click the project in the project browser and select "Generate PhpDoc".
    6. Click Browse and select a directory to generate your documenation in and click OK.
    • EXPECTED RESULT: Documentation is generated in the chosen directory.
Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo