-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[ TS-SELENIUM ] Investigating new typescript related test framework #13200
Conversation
Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com>
Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com>
Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com>
Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com>
Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com>
Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com>
Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com>
Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com>
Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com>
Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com>
Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com>
Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com>
Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com>
Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com>
Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com>
Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com>
Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com>
Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com>
Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com>
Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com>
ci-test |
Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com>
Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com>
Results of automated E2E tests of Eclipse Che Multiuser on OCP: |
Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com>
Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com>
ci-build |
Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com>
|
||
|
||
@injectable() | ||
export class NewWorkspace { |
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.
What about changing the name to e.g. WorkspaceHandler
and include the methods stopWorkspaceByUI
and deleteWorkspaceByUI
here too, so all the logic arount handling the workspace will be on once place? Or is there some reason to have it separated?
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.
The "NewWorkspace" pageobject describes "NewWorkspace" page
}) | ||
|
||
test("Add 'Java Language Support' plugin to workspace", async () => { | ||
await workspaceDetailsPlugins.addPluginAndOpenWorkspace(namespace, workspaceName, javaPluginName, pluginId) |
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.
Maybe I'll split this logic to two lines: addPlugins
and openWorksapce
because I don't think these operations are atomic and we maybe could want to add more plugins before opening workspace.
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.
Yes, you are right, but we can't check that plugins are successfully added until workspace been run.
@@ -32,6 +32,14 @@ export class ProjectTree { | |||
return `${this.getExpandIconLocator(itemPath)}:not(.theia-mod-collapsed)`; | |||
} | |||
|
|||
private getExpandIconLocator(itemPath: string) { |
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.
@Ohrimenko1988 are you going to address this?
const pageSourceFileName: string = `${testReportDirPath}/pagesource-${testTitle}.html` | ||
|
||
//create reporter dir if not exist | ||
await fs.exists(reportDirPath, async isDirExist => { |
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.
From Node.js v10.12 you can use recursive version of mkdir
which IMHO doesn't do anything if the directory already exists. Isn't fs.exists()
call unnecessary? BTW v10 is now active LTS release so I suggest to use it.
ci-build |
Let's merge this PR and fix the technical debts refactorings in a separate PR |
Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com>
Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com>
Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com>
Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com>
hello, what are the CQs for all the dependencies used in that PR ? |
Hello, CQ's for dependencies are in the pending state |
What does this PR do?
Implements new test solution (selenium-typescript + Mocha + Chai). And moves existed "Cypress" codebase to this framework
What issues does this PR fix or reference?
Issue: #13114
Release Notes
Docs PR