-
Notifications
You must be signed in to change notification settings - Fork 68
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
[LIT-2333] Add e2e test for initializing multiple clients #331
Merged
Ansonhkg
merged 3 commits into
staging/2024-02-06
from
feature/lit-2333-add-support-for-initializing-global-lit-variables-under
Feb 2, 2024
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
30 changes: 30 additions & 0 deletions
30
e2e-nodejs/group-connection/test-connection-multi-network.mjs
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
import path from 'path'; | ||
import { success, fail, testThis, log } from '../../tools/scripts/utils.mjs'; | ||
import { LitNodeClient } from '@lit-protocol/lit-node-client'; | ||
|
||
export async function main() { | ||
const networks = ['cayenne', 'habanero', 'manzano']; | ||
|
||
for (const network of networks) { | ||
// ==================== Test Logic ==================== | ||
const client = new LitNodeClient({ | ||
litNetwork: network, | ||
debug: globalThis.LitCI.debug, | ||
}); | ||
log(`connecting to ${network.toUpperCase()}...`); | ||
await client.connect(); | ||
|
||
// ==================== Post-Validation ==================== | ||
if (!client.ready) { | ||
return fail('client not ready'); | ||
} | ||
if (client.config.litNetwork !== network) { | ||
return fail(`client not connected to ${network}`); | ||
} | ||
} | ||
|
||
// ==================== Success ==================== | ||
return success(`Connected to ${networks.join(', ')}`); | ||
} | ||
|
||
await testThis({ name: path.basename(import.meta.url), fn: main }); |
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we add a check on
globalThis
to assert on the new global namespacing?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't implement the global namespacing, I think it's a risky approach (see also #331 (comment)). There could be a use case for global namespaces I'm not aware of yet: in that case please let me know.