TS 72 CNDRemoteDevelopment
C/C++ Pack Test Specification for Remote Development
Author: Alexander Pepin
Version: 0.1
Lastupdate: 28.03.2012
Introduction: Test specification for Remote Development support in NetBeans 7.2 C/C++ Pack
Setup: On Windows install Cygwin or MinGW + MSYS. See C++ setup instructions
Important: On Windows all tests should be done using both Cygwin and MinGW tools
Contents |
Test suite: Add Build Host
- Add Build host via Services
- Open Services tab
- Expand C/C++ Build Hosts node
- check what hosts are listed (for the first time only localhost should be in the list)
- Call "Add New Host" from the context menu on C/C++ Build Hosts node
- EXPECTED RESULT: New Remote Build Host dialog should appear
- Enter host name into Hostname field and change Port if it's needed then press Next
- enter Login and choose Authentication type
- EXPECTED RESULT: If Password was chosen then Authentication dialog should appear
- Enter the password
- When host setting is done verify information on Summary step
- Display Name
- Platform
- Hostname
- User account
- Tool Collections details
- Default Tool Collection (OracleSolarisStudio if exists, GNU otherwise)
- Access ProjectFiles via (System Level File Sharing on Unix/Linux, Automatic copying on Windows)
- Press Finish button to close New Remote Build Host dialog
- EXPECTED RESULT: The newly added host in "Connected" state should appear in the list of hosts under C/C++ Build Hosts node
- Expand the newly added host node and inner Tool Collection node
- Verify that tool collections were added properly
- Add Build host via Tools/Options
- Open Tools->Options->C/C++
- Press Edit button next to Development Host combobox
- EXPECTED RESULT: Build Host Manager dialog should appear
- Press Add button
- EXPECTED RESULT: New Remote Build Host dialog should appear
- Enter host name into Hostname field and change Port if it's needed then press Next
- enter Login and choose Authentication type
- EXPECTED RESULT: If Password was chosen then Authentication dialog should appear
- Enter the password
- When host setting is done verify information on Summary step
- Display Name
- Platform
- Hostname
- User account
- Tool Collections details
- Default Tool Collection (OracleSolarisStudio if exists, GNU otherwise)
- Access Project Files via (System Level File Sharing on Unix/Linux, Automatic copying on Windows)
- Press Finish button to close New Remote Build Host dialog
- Press OK button to close Build Host Manager dialog
- Select the newly added host in Development Host combobox
- Check available tool collections for the selected Build host
- Close Options dialog
Test suite: Create Remote Project
Setup: Shared directories should be created on Unix systems. Samba should be used to allow shared project creation from Windows.
Important: All testcases should be checked using both types of project files accessing (System Level File Sharing and Automatic copying)
- Create Sample Remote Project
- Add build host using appropriate type of project files accessing
- Call "New Project"
- Choose Samples->C/C++ category
- Choose one of the sample projects
- Welcome
- Arguments
- Subproject Application
- Quote
- Press Next
- Select appropriate Build host
- Select appropriate Tool Collection
- Choose appropriate Project Name and Project Folder
- Press Finish
- EXPECTED RESULT: A new sample project with chosen name should appear in Projects
- Open Project Properties for the newly created project
- Verify that Build section shows properties properly
- Create Makefile based Remote Project
- Extract project files from quote_mkfb.tar (Media:Quote mkfb.tar) to an appropriate place (local folder for "Automatic copying" testing or shared folder for "System Level File Sharing")
- Call "New Project"
- Choose C/C++ category
- Choose "C/C++ Project with Existing Sources" projects
- Specify the folder containing existing sources (path to Quote_mkfb folder)
- Select appropriate Build host
- Select Automatic configuration mode
- Press Finish
- Edit Path's Map if it's required
- EXPECTED RESULT: A new Quote_mkfb project should appear in Projects
- Verify that the project node contains Quote_mkfb folder subnode with all project files and Important Files subnode contains Makefile
- Open Project Properties for the newly created project
- Verify that Build section shows properties properly
Test suite: Build and Run Remote Project
Important: All testcases should be checked using both types of project files accessing (System Level File Sharing and Automatic copying)
- Build and Run Remote sample project
- Create Sample project (see "Create Remote Project" testsuite)
- Call Clean and Build
- EXPECTED RESULT: The build process should start. Output window should show Clean and Build tabs with logs. The build should be SUCCESSFUL
- Call Run
- EXPECTED RESULT: Output window should show "<project_name>(Build,Run)-<login>@<host>" tab with build log and "<project_name>(Run)-<login>@<host>" tab with project output
- Modify the project code (e.g. add some output)
- Perform Run again
- EXPECTED RESULT: The project output should be changed according to your modification
- Build and Run Remote makefile based project
- Create Makefile based project (see "Create Remote Project" testsuite)
- Open Project Properties
- Verify that Build Result property in Build/Make section shows right path to executable
- Call Clean and Build
- EXPECTED RESULT: The build process should start. Output window should show "<project_name>(Clean,Build)-<login>@<host> tab with log. The build should be SUCCESSFUL
- Call Run
- EXPECTED RESULT: Output window should show "<project_name>(Build,Run)-<login>@<host>" tab with build log and "<project_name>(Run)-<login>@<host>" tab with project output
- Do some input then finish execution
- Modify the project code (e.g. add some output)
- Do Clean and Build
- Perform Run again
- EXPECTED RESULT: The project output should be changed according to your modification
Test suite: Debug Remote Project
Important: All testcases should be checked using both types of project files accessing (System Level File Sharing and Automatic copying )
- Debug Remote sample project
- Create Sample project (see "Create Remote Project" testsuite)
- Build the project (see "Build and Run Remote Project" testsuite)
- Perform testsuites described in CND Debugger Test specification
- Debug Remote makefile based project
- Create Makefile based project (see "Create Remote Project" testsuite)
- Build the project (see "Build and Run Remote Project" testsuite)
- Perform testsuites described in CND Debugger Test specification
Attachments