-
Notifications
You must be signed in to change notification settings - Fork 28
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
Test writing process improvements #85
Comments
Will authoring tests in Excel be the long term solution? If not, it may be prudent to start work on an alternative sooner rather than later. |
@mfairchild365 commented:
I've been giving this some thought. At first, I thought Excel might be a good solution for at least the medium term, but after having gone through the process of reviewing test plans, I really think not. Writing test plans is hard, even harder to get right than I anticipated. There is going to be lots and lots and lots of revising, even after we have significant experience writing them. I am anticipating that we will get quite a bit of feedback on the plans. So, if we had to rely on Excel imports to do all that work, it would get very time consuming. The number of times I wished to myself, "Dang, where is the edit button for this test" is already pretty significant. Our current test plan review pages are pretty nice. I can easily imagine an "Add Test" button next to the H1 at the top, and an "Edit test" button next to each H2. In short, I think we need to invest in a test composer/editor. In the meantime, @spectranaut, can you give @jongund some requirements for modifying his script so that we can at least make importing reasonably efficient in the near term? That would enable us to keep moving forward with test writing until we have the infrastructure in place to build a test composer and keep you focused on building that infra. |
Ok, advice for @jongund about the script:
|
Thank you for the feedback. |
Currently, the process for converting spreadsheets to tests is pretty wonky, and it took me hours to convert Matt's combobox tests using Jon's scripts. The process as we have it right now:
npm review tests
(a node script) to create test plans from the test files.I'd like to propose we do the following instead:
I didn't do this yet because I wanted people to have experience writing tests before we locked down a test writing process. So my main question is: Do we want to write tests in excel sheets that Jon and Yohta designed, and Matt has now used? If we do this, we will have to be very strict with the excel sheet format, but the test conversion script can also tell you if your excel sheet is formatted incorrectly.
The text was updated successfully, but these errors were encountered: