-
Notifications
You must be signed in to change notification settings - Fork 31
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
Specify test run parameters on command-line #706
Comments
@YashUoM Would you be interested in working on this? |
Sounds great. But my schedule is pretty packed up till the middle of June. After that I can work on this. :) |
That would be great. |
@YashUoM Are you still interested in working on this? I'm looking at growing the team so it's not so dependent on me! |
Hi Charlie, |
It's not a critical feature, so there's no big hurry. I could suggest how to break it into small steps, in case you can only devote a small amount of time each week to working on it. So it's a question of how much time and interest you have. |
I can work 6-10 hours a week given my day job taking my week days. If that's enough I'll start on this. :-) |
Definitely! I have assigned it to you. I'll add you to the team as well, which will give you commit authority, but I want to send you some info about how we operate first. If you send me a note, I'll reply with what you need to know to get started. |
nice :D
…________________________________
From: CharliePoole ***@***.***>
Sent: Monday, September 13, 2021 22:52
To: TestCentric/testcentric-gui ***@***.***>
Cc: Subscribed ***@***.***>
Subject: Re: [TestCentric/testcentric-gui] Specify test run parameters on command-line (#706)
Definitely! I have assigned it to you. I'll add you to the team as well, which will give you commit authority, but I want to send you some info about how we operate first. My email is charliepoole AT gmail DOT com - if you send me a note at that address, I'll reply with what you need to know to get started.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#706 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AA2OH3LNCH56GLHPLDCWOXDUB3BHTANCNFSM443XAWBA>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
@immeraufdemhund Indeed! But still plenty of stuff left to do if you feel like becoming active again. :-) |
Sure. Will drop a mail. And I copied your mail. You can remove it from the comment if you want. :-) |
I'm reopening this. The code I added does solve the problem, but only partially. The gui model creates a test package containing the proper Underlying this is the fact that creation of the test package resides within the model assembly as does the definition of the supported command-line options. There is a need for some serious refactoring to get these definitions to live where they belong, but that's a good thing as it will simplify the model. I'll create a separate issue for that, however. |
🎉 This issue has been resolved in version 2.0.0-alpha7 🎉 The release is available on: |
This came up in the discussion of #703 as something that may be useful.
We should allow syntax similar to NUnit-Console...
Each use may only supply one parameter but the option may appear multiple times. The entire list is added to the TestPackage on load and remains active unless the user makes changes in the GUI parameters dialog.
The text was updated successfully, but these errors were encountered: