-
Notifications
You must be signed in to change notification settings - Fork 195
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
Move API tests to this repo #1047
Open
farshidz
wants to merge
43
commits into
mainline
Choose a base branch
from
farshid/restructure-tests
base: mainline
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
farshidz
had a problem deploying
to
marqo-test-suite
November 21, 2024 02:57 — with
GitHub Actions
Failure
farshidz
had a problem deploying
to
marqo-test-suite
November 21, 2024 02:57 — with
GitHub Actions
Error
farshidz
had a problem deploying
to
marqo-test-suite
November 21, 2024 02:58 — with
GitHub Actions
Failure
farshidz
had a problem deploying
to
marqo-test-suite
November 21, 2024 03:13 — with
GitHub Actions
Error
farshidz
had a problem deploying
to
marqo-test-suite
November 21, 2024 03:13 — with
GitHub Actions
Error
farshidz
had a problem deploying
to
marqo-test-suite
November 21, 2024 03:14 — with
GitHub Actions
Failure
farshidz
force-pushed
the
farshid/restructure-tests
branch
from
November 21, 2024 03:36
ec5ffc8
to
2849cc2
Compare
farshidz
temporarily deployed
to
marqo-test-suite
November 21, 2024 03:38 — with
GitHub Actions
Inactive
farshidz
temporarily deployed
to
marqo-test-suite
November 21, 2024 03:38 — with
GitHub Actions
Inactive
farshidz
had a problem deploying
to
marqo-test-suite
November 21, 2024 03:39 — with
GitHub Actions
Failure
farshidz
temporarily deployed
to
marqo-test-suite
November 21, 2024 05:26 — with
GitHub Actions
Inactive
farshidz
had a problem deploying
to
marqo-test-suite
November 21, 2024 05:26 — with
GitHub Actions
Failure
farshidz
had a problem deploying
to
marqo-test-suite
December 11, 2024 06:22 — with
GitHub Actions
Failure
farshidz
temporarily deployed
to
marqo-test-suite
December 11, 2024 06:22 — with
GitHub Actions
Inactive
farshidz
had a problem deploying
to
marqo-test-suite
December 11, 2024 06:22 — with
GitHub Actions
Failure
farshidz
temporarily deployed
to
marqo-test-suite
December 11, 2024 06:37 — with
GitHub Actions
Inactive
farshidz
had a problem deploying
to
marqo-test-suite
December 19, 2024 05:23 — with
GitHub Actions
Error
farshidz
had a problem deploying
to
marqo-test-suite
December 19, 2024 05:23 — with
GitHub Actions
Failure
farshidz
had a problem deploying
to
marqo-test-suite
December 19, 2024 05:23 — with
GitHub Actions
Failure
farshidz
had a problem deploying
to
marqo-test-suite
December 19, 2024 05:24 — with
GitHub Actions
Failure
farshidz
had a problem deploying
to
marqo-test-suite
December 19, 2024 05:45 — with
GitHub Actions
Failure
farshidz
had a problem deploying
to
marqo-test-suite
December 19, 2024 05:45 — with
GitHub Actions
Failure
farshidz
had a problem deploying
to
marqo-test-suite
December 19, 2024 05:45 — with
GitHub Actions
Error
farshidz
temporarily deployed
to
marqo-test-suite
December 19, 2024 05:54 — with
GitHub Actions
Inactive
farshidz
had a problem deploying
to
marqo-test-suite
December 19, 2024 05:54 — with
GitHub Actions
Failure
farshidz
temporarily deployed
to
marqo-test-suite
December 19, 2024 05:55 — with
GitHub Actions
Inactive
farshidz
temporarily deployed
to
marqo-test-suite
December 19, 2024 23:28 — with
GitHub Actions
Inactive
farshidz
had a problem deploying
to
marqo-test-suite
December 19, 2024 23:28 — with
GitHub Actions
Failure
farshidz
temporarily deployed
to
marqo-test-suite
December 19, 2024 23:28 — with
GitHub Actions
Inactive
farshidz
had a problem deploying
to
marqo-test-suite
December 20, 2024 02:08 — with
GitHub Actions
Error
farshidz
temporarily deployed
to
marqo-test-suite
December 20, 2024 02:08 — with
GitHub Actions
Inactive
farshidz
had a problem deploying
to
marqo-test-suite
December 20, 2024 02:09 — with
GitHub Actions
Error
farshidz
temporarily deployed
to
marqo-test-suite
December 20, 2024 02:30 — with
GitHub Actions
Inactive
farshidz
temporarily deployed
to
marqo-test-suite
December 20, 2024 02:30 — with
GitHub Actions
Inactive
farshidz
temporarily deployed
to
marqo-test-suite
December 20, 2024 02:31 — with
GitHub Actions
Inactive
Hello @farshidz , I noticed you moved all the exisiting unit and integ tests to the integ_tests folder. What is the plan to distinguish integ tests from unit tests going forward? |
Unit tests will be in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Improvement/refactoring
What is the current behavior? (You can also link to an open issue here)
API tests in another repo
What is the new behavior (if this is a feature change)?
API tests moved to the Marqo repo. We will decommission the API tests repo
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No
Have unit tests been run against this PR? (Has there also been any additional testing?)
Related Python client changes (link commit/PR here)
Related documentation changes (link commit/PR here)
Other information:
Please check if the PR fulfills these requirements