TS 61 ProjectsProperties

Projects Test Specification for Projects Properties

Author: Tomas Musil
Last update: 02.05.2008
Introduction: Tests properties of J2Se project


Contents


Test suite: Sources panel

Purpose: Tests sources panel
Setup: Start with fresh userdir. Create some sample project e.g. Anagrams game

  1. Add sourceroot
    1. Add some sourceroot to project (folder with packages/classes)
    • EXPECTED RESULT: New node appears under project node, when you build project, JAR must contain classes from both sourceroots.
  1. Add testroot
    1. Add some testroot to project (folder with packages/classes)
    • EXPECTED RESULT: New node appears under project node, when you invoke Test project, tests from both testroots must be executed
  1. Remove sourceroot and testroot
    1. Remove sourceroot and testroot added in previous testcases
    • EXPECTED RESULT: Project state is restored back to original.
  1. Sourcelevel
    1. Set sourcelevel to 1.4
    2. Type into java file some code compliant with 1.5 (.e.g use generics, for each loops)
    • EXPECTED RESULT: Project is not compilable unless you increase sourcelevel to 1.5.
  1. Include/exclude
    1. try to exclude e.g. *.java files from project (**/*.java)
    • EXPECTED RESULT: Java files are excluded from project, are not visible.


Test suite: Libraries panel

Purpose: Tests libraries panel
Setup: Start with fresh userdir.Create some sample project e.g. JavaApplication

  1. Add new JDK platform
    1. Invoke Java platform manager by Manage platforms button in project properties in libraries panel.
    2. Add new platform - browse for JDK folder
    3. Associate sources with platform (eventually add javadoc for JDK)
    4. Select newly added JDK in combobox, build project.
    • EXPECTED RESULT: Project is built by this JDK. Check that also Navigate
  1. Build projects on classpath
    1. Create project A, project B
    2. Add dependency A depens on B
    3. Use some class of B in sources of A
    4. Uncheck Build projects on classpath
    5. Clean both projects
    6. Build A -> compilation should fail
    7. Check Build projects on classpath
    8. Build A
    • EXPECTED RESULT: Compilation should succeed now.

Test suite: Build|Compiling panel

Purpose: Tests compiling panel
Setup: Start with fresh userdir. Create some sample project e.g. Anagrams game

  1. Generate debugging info
    1. Uncheck Generate debugging info
    2. Clean and build project, place breakpoint somewhere in code
    • EXPECTED RESULT: You should not be able run debugger.
  2. Report uses of deprecated APIs
    1. Check Report uses of deprecated APIs
    2. Use some deprecated code (e.g. javax.swing.JFrame.show() )
    3. Clean and build project
    • EXPECTED RESULT: You should not be notified about deprecation.
  3. Track java dependencies TODO
    1. TODO
    • EXPECTED RESULT: TODO.
  4. Complier options
    1. Check that e.g. "-verbose" complier option takes an effect
    • EXPECTED RESULT: Output during build is verbose

Test suite: Build|Packaging panel

Purpose: Tests packaging panel
Setup: Start with fresh userdir. Create some sample project e.g. Anagrams game

  1. Exclude from JAR file
    1. Remove the pattern for excluding *.java files
    2. Clean and build project
    • EXPECTED RESULT: JAR should contatin also *.java files.
  2. Compress JAR file
    1. Check Compress JAR file
    2. Clean and build project
    • EXPECTED RESULT: Size of JAR file should be smaller now.
  3. Build JAR after compiling
    1. Uncheck Build JAR after compiling
    2. Clean and build project
    • EXPECTED RESULT: Only *.class files should be produced, no JAR file

Test suite: Build|Documenting panel

Purpose: Tests documenting panel
Setup: Start with fresh userdir. Create some sample project e.g. Anagrams game

  1. Javadoc options
    1. Check that all checkboxes work (build javadoc for each case by Generate Javadoc action on project node)
    2. Add some Browser window title
    3. Add some additional options (e.g. -verbose)
    • EXPECTED RESULT: Javadoc is always built according to settings



Test suite: Run panel

Purpose: Tests run panel
Setup: Start with fresh userdir. Create some sample project e.g. Anagrams game

  1. New configuration
    1. Create new configuration
    2. Change parameters (e.g. choose another main class, change the arguments, work dir,..)
    3. Run project
    • EXPECTED RESULT: Project is ran in your configuration
  2. Change configuration
    1. Check that configuration can be switched/customized from configuration combobox in toolbar
    2. Run project
    • EXPECTED RESULT: Project is ran in configuration that is selected in toolbar
  3. Delete configuration
    1. Delete configuation
    • EXPECTED RESULT: Configuration disappears from combobox in toolbar
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