TS 72 CNDRemoteDevelopment

Revision as of 14:26, 5 April 2012 by Apepin (Talk | contribs)

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

Comment:

  1. Add Build host via Services
    1. Open Services tab
    2. Expand C/C++ Build Hosts node
      • check what hosts are listed (for the first time only localhost should be in the list)
    3. Call "Add New Host" from the context menu on C/C++ Build Hosts node
      • EXPECTED RESULT: New Remote Build Host dialog should appear
    4. Enter host name into Hostname field and change Port if it's needed then press Next
    5. enter Login and choose Authentication type
      • EXPECTED RESULT: If Password was chosen then Authentication dialog should appear
      • Enter the password
    6. 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)
    7. 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
    8. Expand the newly added host node and inner Tool Collection node
    9. Verify that tool collections were added properly
  2. Add Build host via Tools/Options
    1. Open Tools->Options->C/C++
    2. Press Edit button next to Development Host combobox
      • EXPECTED RESULT: Build Host Manager dialog should appear
    3. Press Add button
      • EXPECTED RESULT: New Remote Build Host dialog should appear
    4. Enter host name into Hostname field and change Port if it's needed then press Next
    5. enter Login and choose Authentication type
      • EXPECTED RESULT: If Password was chosen then Authentication dialog should appear
      • Enter the password
    6. 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)
    7. Press Finish button to close New Remote Build Host dialog
    8. Press OK button to close Build Host Manager dialog
    9. Select the newly added host in Development Host combobox
    10. Check available tool collections for the selected Build host
    11. 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 )

  1. Create Sample Remote Project
    1. Add build host using appropriate type of project files accessing
    2. Call "New Project"
    3. Choose Samples->C/C++ category
    4. Choose one of the sample projects
      • Welcome
      • Arguments
      • Subproject Application
      • Quote
    5. Press Next
    6. Select appropriate Build host
    7. Select appropriate Tool Collection
    8. Choose appropriate Project Name and Project Folder
    9. Press Finish
      • EXPECTED RESULT: A new sample project with chosen name should appear in Projects
    10. Call Project Properties for the newly created project
    11. Verify that Build section shows properties properly
  2. Create Makefile based Remote Project


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 )

  1. Build and Run Remote sample project
    1. Create Sample project (see "Create Remote Project" testsuite)
    2. 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
    3. 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
    4. Modify the project code (e.g. add some output)
    5. Perform Run again
      • EXPECTED RESULT: The project output should be changed according to your modification
  2. Build and Run Remote makefile based project


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 )

  1. Debug Remote sample project
    1. Create Sample project (see "Create Remote Project" testsuite)
    2. Build the project (see "Build and Run Remote Project" testsuite)
    3. Perform testsuites described in See CND Debugger Test specification
  2. Debug Remote makefile based project
    1. Create Makefile based project (see "Create Remote Project" testsuite)
    2. Build the project (see "Build and Run Remote Project" testsuite)
    3. Perform testsuites described in See CND Debugger Test specification


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