Skip to content

Add manual smoke test plans for MS Office, Libre Office, Web Browsers, IDEs #18419

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
142 changes: 142 additions & 0 deletions tests/manual/applications/IDEs/jetBrains.md
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not a JetBrains user, so some of these comments may be obvious to experienced JetBrains users

Original file line number Diff line number Diff line change
@@ -0,0 +1,142 @@
# JetBrains IDEs Smoke Testing Plan

## Objective

To ensure NVDA functions correctly with JetBrains IDEs (IntelliJ IDEA, Android Studio, PyCharm, WebStorm, etc.) across typical developer workflows.
This plan focuses on basic navigation, project operations, editor accessibility, and common IDE features.
JetBrains IDEs are based on the IntelliJ Platform, which is written in Java and smoke testing can reveal issues with the framework and Java applications more broadly.

## Areas Covered

* Application launch and window navigation
* Project operations
* Editor accessibility
* Search and navigation
* Debugging
* Version control
* Settings and plugins

## 1. Application Launch and Window Navigation

### Steps

1. Launch the JetBrains IDE
1. Verify NVDA announces the IDE window title
1. Use `alt+1` to focus the Project tool window
1. Use `alt+2` to focus the Favorites tool window
1. Use `alt+3` to focus the Find tool window
1. Use `alt+4` to focus the Run tool window
1. Use `alt+5` to focus the Debug tool window
1. Use `alt+6` to focus the TODO tool window
1. Use `alt+7` to focus the Structure tool window
1. Use `alt+8` to focus the Services tool window
1. Use `alt+9` to focus the Version Control tool window
1. Use `ctrl+tab` to switch between open files/tabs

### Expected Results

* NVDA announces window title and major UI regions
* Navigation between tool windows and tabs is clear and consistent

## 2. Project Operations

### Steps

1. Use `ctrl+shift+n` to create a new project
1. Use `ctrl+o` to open an existing project
1. Use `ctrl+shift+o` to open a project from version control
1. Use `ctrl+shift+s` to save all files
1. Use `ctrl+s` to save the current file
1. Use `ctrl+shift+a` to add a new file to the project
1. Use `delete` to remove a file from the project

### Expected Results

* NVDA announces project dialogs, project structure, and file actions
* Project operations are accessible and confirmed by speech

## 3. Editor Accessibility

### Steps

1. Type and navigate code in the editor using arrow keys
1. Use `ctrl+home` and `ctrl+end` to jump to start/end of file
1. Use `ctrl+f` to open the find dialog and search for text
1. Use `ctrl+r` to open the replace dialog
1. Use `ctrl+z` and `ctrl+y` to undo/redo
1. Use `ctrl+shift+space` for parameter info
1. Use `ctrl+space` for code completion
1. Use `ctrl+b` to go to declaration or usage
1. Use `ctrl+shift+b` to go to type declaration
1. Use `ctrl+u` to go to super method
1. Use `ctrl+alt+leftArrow` and `ctrl+alt+rightArrow` to navigate back and forward

### Expected Results

* NVDA announces line numbers, code, and search results
* Editing, navigation, and code assistance features are accessible

## 4. Search and Navigation

### Steps

1. Use `ctrl+f` to search within the current file
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You already had us do that in Editor Accessibility step 3

1. Use `ctrl+shift+f` to search across the project
1. Use `ctrl+shift+n` to find any file, class, or symbol
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You said ctrl+shift+n creates a new project in Project Operations step 1.

1. Use `ctrl+n` to find a class
1. Use `ctrl+shift+n` to find a file
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You already had us use ctrl+shift+n to "find any file, class, or symbol"

1. Use `ctrl+shift+alt+n` to find a symbol
1. Use `ctrl+g` to go to a specific line
1. Use `ctrl+shift+a` to find an action

### Expected Results

* NVDA announces search dialogs, results, and navigation targets
* All search and navigation features are accessible

## 5. Debugging

### Steps

1. Use `f9` to toggle a breakpoint
1. Use `f8` to step over, `f7` to step into, `shift+f8` to step out
1. Use `f9` to resume program execution
1. Use `ctrl+f2` to stop debugging
1. Use `alt+5` to focus the Debug tool window
1. Use `alt+4` to focus the Run tool window
1. Use `ctrl+shift+f8` to view breakpoints

### Expected Results

* NVDA announces debugging state, breakpoints, and window focus
* Stepping, breakpoints, and variable inspection are accessible

## 6. Version Control

### Steps

1. Use `alt+9` to focus the Version Control tool window
1. Use `ctrl+k` to commit changes
1. Use `ctrl+t` to update project from version control
1. Use `ctrl+shift+k` to push changes
1. Use `ctrl+shift+a` to find version control actions

### Expected Results

* NVDA announces version control dialogs and actions
* All version control operations are accessible

## 7. Settings and Plugins

### Steps

1. Use `ctrl+alt+s` to open Settings/Preferences
1. Navigate through settings categories using arrow keys
1. Use `ctrl+alt+s` to open Plugins settings
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You already had us use ctrl+alt+s to open settings

1. Use arrow keys to browse available plugins
1. Use `enter` to install or enable a plugin

### Expected Results

* NVDA announces settings categories and plugin names
* Settings and plugin management are accessible
117 changes: 117 additions & 0 deletions tests/manual/applications/IDEs/notepadPlusPlus.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,117 @@
# Notepad++ Smoke Testing Plan

## Objective

To ensure NVDA functions correctly with Notepad++ across typical user workflows.
This plan focuses on basic navigation, file operations, editor accessibility, and common text editing tasks.
Notepad++ is based on Scintilla and smoke testing can reveal issues with the framework.

## Areas Covered

* Application launch and window navigation
* File operations (open, save, close)
* Editor accessibility
* Search and replace
* Multiple tabs and documents
* Plugins and settings

## 1. Application Launch and Window Navigation

### Steps

1. Launch Notepad++
1. Verify NVDA announces the Notepad++ window title
1. Use `ctrl+tab` to switch between open documents/tabs
1. Use `ctrl+shift+tab` to switch in reverse order
1. Use `ctrl+w` to close the current tab
1. Use `ctrl+n` to create a new document
1. Use `ctrl+o` to open an existing file

### Expected Results

* NVDA announces window title and major UI regions
* Navigation between tabs and documents is clear and consistent

## 2. File Operations

### Steps

1. Use `ctrl+n` to create a new file
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You already had us do this in Application Launch and Window Navigation step 6

1. Type sample text
1. Use `ctrl+s` to save, enter a filename, and confirm
1. Use `ctrl+o` to open an existing file
1. Use `ctrl+w` to close the current file
Comment on lines +42 to +43
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Already done in Application Launch and Window Navigation

1. Use `ctrl+shift+s` to save as
1. Use `ctrl+shift+o` to open in another instance

### Expected Results

* NVDA announces file dialogs and file actions
* File operations are accessible and confirmed by speech

## 3. Editor Accessibility

### Steps

1. Type and navigate text in the editor using arrow keys
1. Use `ctrl+home` and `ctrl+end` to jump to start/end of file
1. Use `ctrl+upArrow` and `ctrl+downArrow` to scroll without moving cursor
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note that doing so causes the current line to be reread if the cursor isn't forced to move by scrolling off screen

1. Use `ctrl+leftArrow` and `ctrl+rightArrow` to move by word
1. Use `shift+arrowKeys` to select text
1. Use `ctrl+a` to select all text
1. Use `ctrl+z` and `ctrl+y` to undo/redo

### Expected Results

* NVDA announces line numbers, text, and cursor position
* Editing and navigation are accessible

## 4. Search and Replace

### Steps

1. Use `ctrl+f` to open the find dialog
1. Enter a search term and use `f3` to find next
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Using f3 with the find dialog open doesn't report anything, as the dialog remains open

1. Use `shift+f3` to find previous
1. Use `ctrl+h` to open the replace dialog
1. Enter search and replace terms
1. Use `alt+a` to replace all
1. Use `alt+r` to replace current
1. Use `ctrl+f3` to find in files

### Expected Results

* NVDA announces search dialogs, results, and replacements
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Many of these operations don't cause announcements, but are still accessible

* All search and replace features are accessible

## 5. Multiple Tabs and Documents

### Steps

1. Open multiple files to create tabs
1. Use `ctrl+tab` to switch between tabs
1. Use `ctrl+shift+tab` to switch in reverse order
1. Use `ctrl+w` to close individual tabs
Comment on lines +92 to +94
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Already done in Application Launch and Window Navigation

1. Use `ctrl+shift+w` to close all tabs
1. Use `ctrl+shift+t` to reopen closed tab
1. Use `ctrl+shift+s` to save all files

### Expected Results

* NVDA announces tab names and switching between tabs
* Multiple document management is accessible

## 6. Plugins and Settings

### Steps

1. Use `alt+p` to open the Plugins menu
1. Navigate through available plugins
1. Use `f7` to access Settings
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this a default setting? I may have removed it, but it does not work in my copy of NPP

1. Navigate through settings categories
1. Change a simple setting and verify it takes effect

### Expected Results

* NVDA announces plugin names and settings options
* Plugin management and settings are accessible
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Worth noting that there are a lot of problems with mislabelled controls in NPP's settings UI

115 changes: 115 additions & 0 deletions tests/manual/applications/IDEs/visualStudio.md
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not a Visual Studio user, so some of these questions/comments may be obvious to experienced users.

Original file line number Diff line number Diff line change
@@ -0,0 +1,115 @@
# Visual Studio Smoke Testing Plan

## Objective

To ensure NVDA functions correctly with Microsoft Visual Studio (not VS Code) across typical developer workflows.
This plan focuses on basic navigation, solution/project/file operations, code editor accessibility, debugging, and common development tasks.
Visual Studio is based on WinForms and as such smoke testing can reveal issues with the framework.

## Areas Covered

* Application launch and window navigation
* Solution, project, and file operations
* Code editor accessibility
* Debugging
* Search and navigation
* Extensions

## 1. Application Launch and Window Navigation

### Steps

1. Launch Visual Studio
1. Verify NVDA announces the Visual Studio window title
1. Use `alt` to access the menu bar
1. Use `ctrl+tab` to switch between open documents and tool windows
1. Use `ctrl+alt+l` to focus the Solution Explorer
1. Use `ctrl+alt+x` to open the Toolbox
1. Use `ctrl+q` to access Quick Launch

### Expected Results

* NVDA announces window title and major UI regions
* Navigation between panels and tool windows is clear and consistent

## 2. Solution, Project, and File Operations

### Steps

1. Use `ctrl+shift+n` to create a new project
1. Use `ctrl+shift+o` to open an existing project or solution
1. Use `ctrl+shift+s` to save all files
1. Use `ctrl+s` to save the current file
1. Use `ctrl+f4` to close the current document
1. Use `ctrl+shift+a` to add a new item to the project
1. Use `delete` to remove a file from the project

### Expected Results

* NVDA announces file dialogs, project structure, and file actions
* Solution and project operations are accessible and confirmed by speech

## 3. Code Editor Accessibility

### Steps

1. Type and navigate code in the editor using arrow keys
1. Use `ctrl+home` and `ctrl+end` to jump to start/end of file
1. Use `ctrl+f` to open the find dialog and search for text
1. Use `ctrl+h` to open the replace dialog
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Has actually using text replacement intentionally been omitted?

1. Use `ctrl+z` and `ctrl+y` to undo/redo
1. Use `ctrl+shift+space` for parameter info
1. Use `ctrl+space` for code completion
1. Use `f12` to go to definition
1. Use `shift+f12` to find all references

### Expected Results

* NVDA announces line numbers, code, and search results
* Editing, navigation, and code assistance features are accessible

## 4. Debugging

### Steps

1. Use `f5` to start debugging
1. Use `shift+f5` to stop debugging
1. Use `f9` to toggle a breakpoint
1. Use `f10` to step over, `f11` to step into, `shift+f11` to step out
1. Use `ctrl+alt+w,1` to open the Watch window
1. Use `ctrl+alt+q` to open the QuickWatch dialog
1. Use `ctrl+alt+c` to open the Call Stack window

### Expected Results

* NVDA announces debugging state, breakpoints, and window focus
* Stepping, breakpoints, and variable inspection are accessible

## 5. Search and Navigation

### Steps

1. Use `ctrl+f` to search within the current file
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Already done in Code Editor Accessibility

1. Use `ctrl+shift+f` to search across the solution
1. Use `ctrl+comma` to go to any file, symbol, or line
1. Use `ctrl+minus` and `ctrl+shift+minus` to navigate back and forward
1. Use `ctrl+g` to go to a specific line

### Expected Results

* NVDA announces search dialogs, results, and navigation targets
* All search and navigation features are accessible

## 6. Extensions

### Steps

1. Use `ctrl+q` to open Quick Launch, type "extensions"
1. Use arrow keys to navigate to Extensions and Updates
1. Use `tab` and arrow keys to browse available extensions
1. Use `enter` to install or enable an extension

### Expected Results

* NVDA announces extension names, details, and actions
* Installing and managing extensions is accessible
Loading