Alpha test download link downloads differents versions of the application to testers. The version number of the downloaded application is the lastest one but it is missing some functionalities that are in the latest version that I published.
So we tried again to download the latest version of the application through the Internal Testing and Internal app sharing of Google play but we are encountering the same issue.
Has anybody encountered the same issue? Can you assist?
Thank you.
I've saw in https://sonarcloud.io/project/activity?id=ch.ge.ve%3Aadmin-offline%3Adevelopment that the activity page view shows some charts on how the project evolved on time.
I'm using Sonarqube docker 6.4 version and there is no charts on that page and I don't know if it's a version problem or what else.
I'm analyzing php projects. Maybe the problem is here?
Does any one knows what's happening?
An screenshot of the example in https://sonarcloud.io/project/activity?id=ch.ge.ve%3Aadmin-offline%3Adevelopment
Thank you.
Those charts are introduced in 6.5. SonarCloud is running the current 6.5 RC, which is why you see graphs there. Since you're running 6.4, it is normal and expected that you don't have graphs.
Sonarqube 4.1.2 with the latest php-plugin is not detecting any violations.
When I run the analisis with Sonar 4.2 it shows me the errors how I expected them.
Is there a bug related to the php-plugin? Can anyone confirm this behaviour?
Thanks in advance
When using SonarQube 4.1.2, could you double check the content of the PHP quality profile that you're using ? Indeed in latest versions of the PHP plugin, all rules have been rewritten so if you have also upgraded the PHP plugin perhaps you're simply doing an analysis with an empty quality profile.
I have cucumber scripts running currently on chrome browser version 25. A update on chrome version had happened recently and I see that all cucumber jobs are failing. Please advice with necessary changes to be made can overcome this problem
If we choose latest version of Firefox or latest version of Selenium-Webdriver, we couldn't automate few tests because of either something not supported in latest version of Firefox or latest version of Selenium-WebDriver.
In such situation, which combinations of Firefox version and Selenium Webdriver version should we choose? (I mean, should we go for one/two version back of latest Firefox version and/or one/two version back of latest selenium webdriver version or some other combination?)
The Latest piece of softwares are always preferable, But the selection of browser version is highly depend upon your application under test.
For newer versions of selenium (v3), check out the selenium-docker releases here, https://github.com/SeleniumHQ/docker-selenium/releases, you can even use docker to test all the Selenium/Firefox combinations easily. For older versions of selenium (v2), check out the selenium site here, https://www.seleniumhq.org/about/platforms.jsp .
I recommend moving to the docker path for local testing; then you can also use the docker files to migrate to cloud platforms.
Use whatever your acceptance criteria states. If you have to support an earlier version of Firefox because it is in a contract or requirement, then you must test that version and use whatever version of selenium is necessary
When ever you download latest webdriver version, make sure that you look into https://raw.githubusercontent.com/SeleniumHQ/selenium/master/java/CHANGELOG
to check the latest browser version support.