'tap sdk new project' project name not properly validated
If the project name ends with a slash, for example, the generated project is invalid. For example, the .sln and .cs files have invalid names.
Similarly, if the project name starts with a number (or any other character which is not valid in a class name) the generated project will not compile.
We should probably make a basic effort to validate the input.
See log for details:
> alex@alex-virtualbox:~$ ./tap2/tap sdk new project badproj/
Creating project in '/home/alex/badproj/'
Generated file: '/home/alex/badproj/badproj/.sln'.
The solution file keeps track of all the projects in this directory.
When you create new projects in this directory with the 'tap sdk new project' command, they are automatically added to the solution.
Generated file: '/home/alex/badproj/Directory.Build.props'.
'Directory.Build.props' contains solution-wide settings. Its primary purpose is to ensure that all your projects use the same version of OpenTAP, and build into the same directory.
Generated file: '/home/alex/badproj/badproj/badproj/.csproj'.
The '.csproj' file contains the configuration specific to this project.
Generated file: '/home/alex/badproj/badproj/badproj/.cs'.
This is a basic TestStep.
Generated file: '/home/alex/badproj/badproj/package.xml'.
The 'package.xml' file tells OpenTAP which files to package when creating a '.TapPackage'.
When building in release mode, OpenTAP will attempt to build a TapPackage according to the contents of this file.
Alternatively, you can build a package manually with 'tap package create path/to/package.xml'.
After you build this project, OpenTAP will be installed in '/home/alex/badproj/bin/Debug'
Build the project and use an editor to create a test plan to use your new test step! See https://doc.opentap.io/User%20Guide/Editors/ for more info on the different editors!