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
- Add sourceroot
- 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.
- Add testroot
- 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
- Remove sourceroot and testroot
- Remove sourceroot and testroot added in previous testcases
- EXPECTED RESULT: Project state is restored back to original.
- Sourcelevel
- Set sourcelevel to 1.4
- 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.
- Include/exclude
- 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
- Add new JDK platform
- Invoke Java platform manager by Manage platforms button in project properties in libraries panel.
- Add new platform - browse for JDK folder
- Associate sources with platform (eventually add javadoc for JDK)
- Select newly added JDK in combobox, build project.
- EXPECTED RESULT: Project is built by this JDK. Check that also Navigate
- Build projects on classpath
- Create project A, project B
- Add dependency A depens on B
- Use some class of B in sources of A
- Uncheck Build projects on classpath
- Clean both projects
- Build A -> compilation should fail
- Check Build projects on classpath
- 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
- Generate debugging info
- Uncheck Generate debugging info
- Clean and build project, place breakpoint somewhere in code
- EXPECTED RESULT: You should not be able run debugger.
- Report uses of deprecated APIs
- Check Report uses of deprecated APIs
- Use some deprecated code (e.g. javax.swing.JFrame.show() )
- Clean and build project
- EXPECTED RESULT: You should not be notified about deprecation.
- Track java dependencies TODO
- TODO
- EXPECTED RESULT: TODO.
- Complier options
- 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
- Exclude from JAR file
- Remove the pattern for excluding *.java files
- Clean and build project
- EXPECTED RESULT: JAR should contatin also *.java files.
- Compress JAR file
- Check Compress JAR file
- Clean and build project
- EXPECTED RESULT: Size of JAR file should be smaller now.
- Build JAR after compiling
- Uncheck Build JAR after compiling
- 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
- Javadoc options
- Check that all checkboxes work (build javadoc for each case by Generate Javadoc action on project node)
- Add some Browser window title
- 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
- New configuration
- Create new configuration
- Change parameters (e.g. choose another main class, change the arguments, work dir,..)
- Run project
- EXPECTED RESULT: Project is ran in your configuration
- Change configuration
- Check that configuration can be switched/customized from configuration combobox in toolbar
- Run project
- EXPECTED RESULT: Project is ran in configuration that is selected in toolbar
- Delete configuration
- Delete configuation
- EXPECTED RESULT: Configuration disappears from combobox in toolbar