You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 16, 2018. It is now read-only.
using something like selenium to drive the actual web console
talking to the obsidian/forge REST API directly
Which then creates a project using each of the quickstarts/wizard options and then asserts that
the git repo + openshift project is created and the pipeline completes successfully
a user then makes a git commit + push somehow (I guess ideally via Che but for now could just be via git) and then assert that a 2nd pipeline is triggered and it completes successfully
use the new forge-service / obsidian REST API. I wonder if the obsidian folks have something for this already?
use the new obsidian wizards
The code to do asserts on builds completing and whatnot should be similar; though we could just use the OpenShift APIs for all that now via the OpenShiftClient checking the project is created - via the BuildConfig and that the Build starts and completes OK and tails the log etc.
The text was updated successfully, but these errors were encountered:
ideally we'd have 2 kinds of system test:
Which then creates a project using each of the quickstarts/wizard options and then asserts that
Upstream on the fabric8 project we used a slightly different distro of forge + forge addons and have these system tests here:
https://github.com/fabric8io/fabric8-forge/tree/master/fabric8-forge-rest-client
we just need to migrate them to
The code to do asserts on builds completing and whatnot should be similar; though we could just use the OpenShift APIs for all that now via the
OpenShiftClient
checking the project is created - via theBuildConfig
and that theBuild
starts and completes OK and tails the log etc.The text was updated successfully, but these errors were encountered: