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
nip.io status for deployed application #906
Comments
@amitkrout , is your problem of namespace solved ?
This depends on the implementation of your above step definition. What is expected here? Do you have the code staged in any of your branch? |
@amitkrout For http request you can use |
@agajdosi i see. i have not checked that, definitely have a look on that @budhrg No the namespace problem is not yet solved. Currently i am doing some more investigation on it. There migit be a modification in step defination implimentation. Will push it to my local branch once i get a conclusion on that. Also i need to check what @agajdosi suggesting |
I don't understand this step? What does "entry point of namespace "ruby" with https "true" mean? I get "When accessing application "ruby-ex" which might be even clearer by "When accessing route for application "ruby-ex"", but what is the rest? |
+1, at least have a look at it. There is for sure communality. |
@hferentschik If the step is confusing/unclear, that can be changed to a better one but the three string arguments passed to it are compulsory. Here the aim is reuse of existing package rather duplicating the code. The two string and one bool argument is required by the existing function
+1, Will check and validate how it fits to this requirement |
Do we want to check anything else other than just checking the URL is not returning error e.g. 404 ? |
@LalatenduMohanty As per the test scenario the command should execute successfully and returns HTTP status OK else test step will fail. |
Yes..I can see it in a well organize way rather what i was thinking to implement. Now for me it requires less effort to implement my changes. Now the scenario would be look like this Scenario: User can access ruby-ex routing url
Given Minishift has state "Running"
When status code of HTTP request to "Routing" is equal to "200"
Then body of HTTP request to "Routing" contains "ok"
And body of HTTP request to "Routing" contains "<title>Welcome to OpenShift</title>" I have already done the changes but i am facing a problem while running it. This is failing at ERROR: When status code of HTTP request to "Routing" is equal to "200"
Error: Server returned error on url: ruby-ex-ruby.192.168.42.99.nip.io |
@LalatenduMohanty I modified the test step. These steps will validate |
@hferentschik @agajdosi The problem was with the url not with the timing. I just added http:// as a prefix to url
I will send the pr soon |
@amitkrout , cool 👍 |
…a service in a given namespace
Merged via pull request #925. |
In the current integration test we have ruby-ex application deployment scenario. Here the missing part is the response status of the deployed application over the HTTP port to the public domain and is not yet implemented.
In the existing code [1], url can easily be retrieved just by calling the function
func GetServiceURL
. So the test scenario would look something like this[1] https://github.com/minishift/minishift/blob/master/pkg/minishift/openshift/service.go
The text was updated successfully, but these errors were encountered: