Skip to content
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

'Disable' not 'Remove' test plans with data #132 #237

Merged
merged 1 commit into from
Apr 26, 2021

Conversation

sayantam
Copy link
Collaborator

Description

As a test plan is uploaded, it can be removed. When it is saved, it can additionally be disabled. When it is executed successfully in a load test, it can only be disabled, not removed.

Linked Issues

Checklist

  • If a new feature is being added, I have added a corresponding post to docs/.
  • I have added tests that prove my fix is effective or that my feature works.
  • New and existing unit tests pass locally with my changes.
  • I have made corresponding changes to the wiki where applicable.

@sayantam sayantam merged commit b93d064 into develop Apr 26, 2021
@sayantam sayantam mentioned this pull request Apr 26, 2021
4 tasks
sayantam added a commit that referenced this pull request Apr 26, 2021
Merge PR #237.

The UI automation failed while trying to click the 'Terminate' button on the AWS setup. The exact same command succeeded for the data center setup. Manually verified that AWS setup can be terminated successfully. Ignoring the false negative from the UI automation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

JMeter file configuration should replace 'Remove' with 'Disable' after it used in a successful test cycle.
1 participant