Describe the bug
When trying to execute to a CSV or TXT file from within the Query Builder, the application crashes.

To Reproduce
Steps to reproduce the behavior:

Expected behavior
Expect that the code ensures that the output from the executed command gets placed into an external file of my choosing.

The dropdown prompt for choosing the format of the output implementation of requirement #79.

Brief Overview

There should exist a button that when pressed, adds new parameter slots to a command.

User Stories / Use Cases

As a user, I want to be able to include as many parameters as I'd like, to retrieve the appropriate data.

Acceptance Criteria

• A button to add additional parameter slots.
• When clicked, new parameter slots appear.

Brief Overview

There must exist some functionality, where when a saved query is selected, it loads all of the commands, title, information, etc.

User Stories / Use Cases

As a user, I want to load saved queries, so I can execute them again.

Acceptance Criteria

List of criteria to meet for the requirement to be considered complete.

Brief Overview

There should exist a button that when pressed, adds a new command slot in the Query Builder.

User Stories / Use Cases

As a user, I want to be able to execute more than one PowerShell command, to get multiple pieces of data.

Acceptance Criteria

• Button
• Functionality

The text box to enter the description of the query, implementation of requirement #53.

The add command slot button implementation of requirement #61.

Describe the bug
Sometimes, when saving a query, the application saves double the number of parameters + values than what was specified in the GUI.

To Reproduce
Steps to reproduce the behavior:

1. Start the application in a new session with no saved queries, and the data file containing saved queries doesn't exist.
2. Go to the "Query Builder" tab, and create and save a new query with the command, parameters, and its value filled out (i.e. Get-ADUser -Filter *.
3. The saved query should now be in the left sidebar.
4. Open the CustomQueries.dat file within the executable's directory.
5. You should now see something similar to the following:

   	{
   		"$id": "1",
   		"$values": [
   		  {
   		    "$id": "2",
   		    "commandName": "Get-ADUser",
   		    "commandParameters": [
   		      "-Filter"
   		    ],
   		    "commandParametersValues": [
   		      "*"
   		    ],
   		    "queryName": "",
   		    "queryDescription": ""
   		  }
   		]
   	}
   

6. Now exit the file and return the application's "Query Builder" tab if you aren't already there.
7. Save the query once more; now, you should see a new saved query in the left sidebar.
8. Once again, open the CustomQueries.dat file.
9. You should now see something like the following:

   	{
   	  "$id": "1",
   	  "$values": [
   	    {
   	      "$id": "2",
   	      "commandName": "Get-ADUser",
   	      "commandParameters": [
   	        "-Filter"
   	      ],
   	      "commandParametersValues": [
   	        "*"
   	      ],
   	      "queryName": "",
   	      "queryDescription": ""
   	    },
   	    {
   	      "$id": "3",
   	      "commandName": "Get-ADUser",
   	      "commandParameters": [
   	        "-Filter",
   	        "-Filter"
   	      ],
   	      "commandParametersValues": [
   	        "*",
   	        "*"
   	      ],
   	      "queryName": "",
   	      "queryDescription": ""
   	    }
   	  ]
   	}
   

10. Notice how the newest query has duplicate command parameters and values.

Expected behavior
I expect that it doesn't duplicate the number of present parameters. I expect it stores the exact number and parameter present in the GUI.

The button implementation of requirement #82.

The clear button implementation of requirement #76.

Describe the bug
After clearing the Query Builder and creating a new query, I face a problem when attempting to execute the query from the Query Button. A notification pops up, stating that the command must be set before the query can be executed, which prevents me from executing the query.

To Reproduce
Steps to reproduce the behavior:

Expected behavior
I expect the program to be still able to execute the query from the Query Stack Panel.

The button to save the title and description of the query, implementation of requirement #53.

Brief Overview

There should exist a button that allows you to export the contents of the console output.

Detailed Description:

When pressing the button, the user should be prompted on what format to want the output to be exported as.

User Stories / Use Cases

As a user, I want to export the output of a command, to review it at a later date.

Acceptance Criteria

• A button to perform the export action.
• A prompt displayed to the user, allowing them to choose the format everything is exported as.

Brief Overview

The dropdown menus in the Query Builder should display Active Directory commands, and provide the appropriate parameters for that command.

User Stories / Use Cases

As an admin, I want to easily access a full list of PowerShell commands and arguments in the Active Directory module, so I don't have to remember every possible command.

Acceptance Criteria

• Several dropdown menus, located in the Query Builder tab/window, that display AD commands and arguments.

The execute button implementation of requirement #64.

The text box implementation of requirement #57.

Brief Overview

There must exist a button such that when pressed, a built query is saved for later use.

User Stories / Use Cases

As a user, I want to save PowerShell queries, so that I can use them again in the future.

Acceptance Criteria

• A button to save the query.
• A section on the GUI where each query is saved and can be selected.
• A physical file that the queries are saved to.
  • The file should be a serialized .dat file.
    • There needs to be an agreed-upon format for this .dat file.

Brief Overview

When executing a PowerShell query, the output text should be displayed in a text box.

Detailed Description:

The text box should not be editable and should be located in the same window/tab that the Query Builder is located in.

User Stories / Use Cases

As a user, I want to view information from a query against Active Directory to see the output of the execute command.

Acceptance Criteria

• A blank, uneditable, text box in the same window/tab that the Query Builder is located in.

The section on the GUI where each query is saved and can be selected, implementation of requirement #72.

The application must be portable/easily moved around. Shouldn't require compiling on system.

Brief Overview

There must exist text boxes to provide a title and description of the query. Additionally, there must be a button that when pressed, saves the query information.

User Stories / Use Cases

As a user, I want to save the description and title of a PowerShell query, to easily identify the purpose of the query.

Acceptance Criteria

There must be:

• A text box to enter the title of the query.
• A text box to enter the description of the query.
• A button that when pressed, saves the text in the title and description text box.

Describe the bug
If you attempt to run a query with a parameter value that is not a string, like a boolean, you will encounter an error. The error message will indicate that it is not possible to convert a string object to a boolean-type object.

To Reproduce
Steps to reproduce the behavior:

Expected behavior
The program should be able to interpret the correct data type and properly pass it through the necessary components

When attempting to execute another command after the initial execution, the output doesn't change or update to reflect the new output of the command.

The confirmation prompted to clear the output console implementation of requirement #76.

The remove command slot button implementation of requirement #61.

The button implementation of requirement #84.

Brief Overview

There exists a button, that when pressed, executes the crafted PowerShell command(s).

Detailed Description:

When there is nothing in the command dropdown, prevent the button from attempting to execute something.

Refer to the "Additional Notes" section for a possible alternative.

Brief Overview

There must exist a drop-down in the query builder, such that the user may choose from a list of users, computers, or IP Addresses, on the domain.

Detailed Description:

This feature will be used to easily select a user or computer to be the target of some PowerShell command.

User Stories / Use Cases

As a user of this application, I want to easily select users or computers on my domain to act against, so I don't have to manually identify a computer or user on the network.

Acceptance Criteria

• Upon selecting a parameter that requires a target, it should either list the computers or users on the network.

Additional Notes

This could also be approached by creating a tab that when selected, will display a page of all users, IPs, and computers on the domain.

The drop-down menu implementation of requirement #59.

The text box to enter the title of the query, implementation of requirement #53.

Brief Overview

There needs to exist a remove and add button that can add and remove command slots.

Detailed Description:

The number of command slots can't be less than one.

Question: Should there be a maximum number of command slots?

User Stories / Use Cases

As an admin, I'd want the option to execute more than one PowerShell command against Active Directory, to perform multiple queries if one command doesn't complete the desired result/job.

Acceptance Criteria

There must be:

• An add button to add a new command slot.
• A remove button to remove a command slot, as long as at least one command slot exists.

The save button implementation of requirement #72.

The export button implementation of requirement #79.

Brief Overview

There should exist a button that clears the output console of all text.

Detailed Description:

The clear console button should prompt the user for confirmation before clearing the console.

User Stories / Use Cases

As a user, I want to clear the console of all output, to reduce clutter to the output.

Acceptance Criteria

• A button to clear the output console.
• The prompt that requires the user to confirm if they want to clear the output console