:iphone: Wrapper Appium Framework in Java which supports Automation of Mobile and Tablet apps.
Home Page: https://wasiqb.github.io/website/projects/coteafs-appium
License: Apache License 2.0
Hi,
It is observed that, user has to manually enter the path as well as the name of the file for the screenshot. So, can we have a dynamic screenshot naming convention, like user has to set the path only, and file name is generated like "SCRddmmyyhhmmss".
With incorporation of latest Appium-Java client, it is required to add support for Windows devices.
It is observed that in case of log file generation,Whenever a new Test is Run, system deletes the old log files and creates a fresh one.
In such a case, if user wants reference to old cases he has tested, he can't get as logs have already been deleted.
Hence, it is suggested to keep the old log files as it is and create a new file on every run.
Also, to overcome the name difficulty, appending Datetimestamp in the logfile name can be handy.
Error displayed in the console is not captured in log file.
my-error-log.log file is generated but it is blank.
Set the log_level to "ERROR" in the appium-config.yaml file and run the test.
##Stack Trace of the failure test:
https://gist.github.com/mfaisalkhatri/5334aa2d436f8cff23d514a0f2a2e716
With release of latest version 5.0.0 of Appium Java client, it is required to implement the following behavior in the framework:
Following are the device level actions which needs to be implemented:
The action will be on device where user can swipe in any direction for a specific distance from the center of the scree.
This action will be combined swipe action where one swipe action will move up and other will move down from the center of the screen till the specified distance.
This action will be combined swipe action where one swipe action will move down and other will move up from the center of the screen till the specified distance.
There are four types of distance defined in the framework:
Following are the element level actions which needs to be modified / added:
This action need to be modified and to be implemented using TouchAction class.
This will be implemented in next release as I am figuring out the possible ways and an effective way to implement it. It's method will throw NotImplementedError.
This will be implemented in next release as I am figuring out the possible ways and an effective way to implement it. It's method will throw NotImplementedError.
This will be implemented in next release as I am figuring out the possible ways and an effective way to implement it. It's method will throw NotImplementedError.
It is required to have video recording of the tests.
Video recording should get started when startRecording method is called and should get end and saved as MP4 when stopRecording method is called.
It is required to add unit tests for the framework in order to ensure smooth functioning of the framework. It is needed to add unit tests using an open sourced app for Android.
DeviceSetting has 110 methods (exceeds 20 allowed). Consider refactoring.
Currently, it is mandatory to run tests on real devices. This needs to be changed and allow the tests to be run on custom simulators / emulators.
Currently Circle CI build are failing due to incorrect config file. This needs to be resolved.
It is required that failed tests should re run automatically, as per the no. of retries given by user in config file
It is suggested to provide the UiAutomator support with this framework.
Windows desktop app support needs to be integrated in the framework.
Currently, when port is not provided in config file and external flag is OFF, then Framework throws AppiumConfigParameterNotFoundError.
It is now required that when external flag is OFF and Port is not available, than Framework should use any available Port.
User should be able to zoom and pinch on elements.
Zoom and Pinch is only functional when Automation name is Espresso.
Same is confirmed in the issue raised for the same here.
System displays the following error when user tries to run the Test using external: false in the config file:
"FAILED CONFIGURATION: @BeforeSuite setupSuite
com.github.wasiqb.coteafs.appium.error.AppiumServerNotStartingError: Error occured while starting Appium server"
Config file details are as follows:
servers:
android:
ip: 127.0.0.1
port: 4723
external: false
arguments:
log_level: DEBUG
log_time_stamp: true
local_time_zone: true
suppress_adb_kill_server: true
Check log files for more details.
Outdated dependencies needs to be updated and unnecessary files needs to be removed.
Logging is done in fixed format and fixed number of log files are generated.
Logging should now be configurable and the user should have more control on it
Need to incorporate coteafs-logger.
ServerArgumentSetting has 32 methods (exceeds 20 allowed). Consider refactoring.
Browser Stack integration is required to run mobile automation tests in cloud or on Grid locally on different mobile OS platform.
Earlier, there was no custom exception in the framework which helps in identifying the problem when the name specified in method onElement does not match the name provided when creating the activity.
To handle this, we need to introduce new Exception named DeviceElementNameNotFoundException.
Currently list view and tables are not supported by the Framework.
This needs to be handled.
System does not allow running tests on Chrome browser in android phone.
In the config file, browser key was added with "chrome" value, and accordingly test was prepared.
Following is the test written to run the chrome browser:
@test
public void test1 () {
final MainActivity main = new MainActivity (this.device);
main.onDevice ().navigateTo ("http://www.facebook.com");
}
https://gist.github.com/mfaisalkhatri/d909cb936fd97308060b46d371f1b437
It is required to implement configurable delays between the following user actions:
Also required to deprecate these methods with delay parameters.
After gemnasium services were closed and moved to GitLab, It is now required to setup the project in GitLab for dependencies monitoring.
Following error is displayed while project building.
"Missing artifact com.github.wasiqb.coteafs:configs:jar:${coteafs.config.version}".
Kindly do the needful.
Build the project.
Project_Build_Error.docx
File DeviceSetting.java has 412 lines of code (exceeds 250 allowed). Consider refactoring.
Test Case: Verify by pressing the Enter Key after entering search text in the search bar of the Flipkart mobile app.
Test Steps: 01. Go to Flipkart App. 02. Tap on search bar, 03. Enter Text "Note 5" and press Enter key.
Expected Output - System should allow to enter text an press "Enter" key.
Actual Output - No method is provided to press "Enter" Key.
(Screenshot of the search window is attached for more details).
System should check the battery health of the device before running tests.
If battery is less than 20%, than tests should not run and message should be logged as "Low battery, please connect to charger and re-run test".
This feature will only be supported when Automation name is UIAutomator2. Refer here for confirmation from Appium maintainers.
Need to incorporate changes for Appium Java Client latest version.
I am getting an issue on iOS device when I switched to NATIVE view and try to back into Webview.
AppiumDriver().getContextHandles();
[HTTP] <-- GET /wd/hub/session/2b68dc2a-59d8-4925-bdd7-89d0ff51e90d/screenshot 200 2068 ms - 2024946
[HTTP]
[HTTP] --> GET /wd/hub/session/2b68dc2a-59d8-4925-bdd7-89d0ff51e90d/context
[HTTP] {}
[debug] [MJSONWP] Calling AppiumDriver.getCurrentContext() with args: ["2b68dc2a-59d8-4925-bdd7-89d0ff51e90d"]
[debug] [XCUITest] Executing command 'getCurrentContext'
[debug] [MJSONWP] Responding to client with driver.getCurrentContext() result: "NATIVE_APP"
[HTTP] <-- GET /wd/hub/session/2b68dc2a-59d8-4925-bdd7-89d0ff51e90d/context 200 2 ms - 84
[HTTP]
[HTTP] --> GET /wd/hub/session/2b68dc2a-59d8-4925-bdd7-89d0ff51e90d/contexts
[HTTP] {}
[debug] [MJSONWP] Calling AppiumDriver.getContexts() with args: ["2b68dc2a-59d8-4925-bdd7-89d0ff51e90d"]
[debug] [XCUITest] Executing command 'getContexts'
[debug] [iOS] Getting list of available contexts
[debug] [iOS] Retrieving contexts and views
[debug] [iOS] Selecting by url: false
[debug] [RemoteDebugger] Getting WebKitRemoteDebugger pageArray: localhost, 27753
[debug] [RemoteDebugger] Sending request to: http://localhost:27753/json
[MJSONWP] Encountered internal error running command: SyntaxError: Unexpected token c in JSON at position 247
[MJSONWP] at JSON.parse ()
[MJSONWP] at WebKitRemoteDebugger.getJsonFromUrl$ (/usr/local/lib/node_modules/appium/node_modules/appium-remote-debugger/lib/webkit-remote-debugger.js:85:22)
[MJSONWP] at tryCatch (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:67:40)
[MJSONWP] at GeneratorFunctionPrototype.invoke [as _invoke] (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:315:22)
[MJSONWP] at GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:100:21)
[MJSONWP] at GeneratorFunctionPrototype.invoke (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:136:37)
[MJSONWP] at
[HTTP] <-- GET /wd/hub/session/2b68dc2a-59d8-4925-bdd7-89d0ff51e90d/contexts 500 7 ms - 213
org.openqa.selenium.WebDriverException: An unknown server-side error occurred while processing the command. Original error: Unexpected token c in JSON at position 247 (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 16 milliseconds
Build info: version: 'unknown', revision: 'unknown', time: 'unknown'
System info: host: 'COMPUTER000117', ip: '192.168.133.60', os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_91'
Driver info: io.appium.java_client.ios.IOSDriver
Capabilities [{app=/Users/admin/Desktop/IPA/TouchClassic_5.0.1.app, networkConnectionEnabled=false, databaseEnabled=false, deviceName=ipad, fullReset=true, platform=MAC, showXcodeLog=true, newCommandTimeout=300, platformVersion=10.3.1, webStorageEnabled=false, locationContextEnabled=false, automationName=XCUITest, browserName=, takesScreenshot=true, javascriptEnabled=true, platformName=iOS, udid=d8a8f24c27769d00627929f291b15eb015e9e8c4, autoAcceptAlerts=true}]
Session ID: 2b68dc2a-59d8-4925-bdd7-89d0ff51e90d
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:206)
at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:158)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:678)
at io.appium.java_client.DefaultGenericMobileDriver.execute(DefaultGenericMobileDriver.java:40)
at io.appium.java_client.AppiumDriver.execute(AppiumDriver.java:235)
at io.appium.java_client.AppiumDriver.getContextHandles(AppiumDriver.java:562)
Currently, Screenshots of the failed tests are not captured. It is suggested to capture the screenshots of the failed tests.
Config file related changes needs to be removed and coteafs-config library needs to be used.
There is no support to add different server argument flags when starting server from Framework which we can do it while starting server externally.
It is now required to provide support to change different server argument flags via config file.
Method start has a Cognitive Complexity of 9 (exceeds 5 allowed). Consider refactoring.
As a Test Engineer, I must be able to Automate all UI using same framework and coding standards. In order to achieve this goal, we need to integrate Selenium WebDriver into the framework for Desktop web app testing.
Swipe on Element is not working.
Please check log file for more details.
Please provide more details or sample code to reproduce the issue, if necessary.
SwipeElementCode - https://gist.github.com/mfaisalkhatri/dcbd12e8f42c9e28520976932c260b02
SwipeElementTest - https://gist.github.com/mfaisalkhatri/c6db24c59731c3159eba94edd6204409
https://gist.github.com/mfaisalkhatri/efedb531f6960abf99817f6d6834ccf5
Main Log file - https://gist.github.com/mfaisalkhatri/64bed9f5022ae124b2100f2d28950cd1
Method setCapability has a Cognitive Complexity of 6 (exceeds 5 allowed). Consider refactoring.
It is required ti provide allure reports integration with coteafs-appium for easy of the user to check reports in detailed format.
Need to solve code issues identified by SonarQube here.
Method buildCapabilities has 26 lines of code (exceeds 25 allowed). Consider refactoring.
Currently, there is no support for mobile web application automation. This needs to be added.
Following browsers needs to be supported:
Many activity have collection of elements which we use together to perform some action like search, add, modify, delete a record. In order to simplify the tests by abstracting the action and reducing code duplication, it is now required to add new class to abstract this behavior.
Users will now extend the newly created Action class to add their activity specific actions.
This class will have 1 abstract method perform which will be implemented by the user and called in the test.
All the elements which will be interacted in the action can be added thru addElement method.
This class will be abstract and will extend 1st class for simplicity.
This class will be abstract and will extend 1st class for simplicity.
When same screen of same app is tested on different devices, we need to create same page object for both the devices. This needs to be handled such that same page object should work for both the devices.
Also user should be able to add different locators for different automation type and different platforms for the same element.
File Device.java has 269 lines of code (exceeds 250 allowed). Consider refactoring.
Currently, we can perform inline verification on an element only once. We need to allow user to perform multiple inline verifications on an element in a single code statement.
Existing sample:
login.onElement ("userName")
.verifyThat ()
.shouldBeEnabled ();New change sample:
login.onElement ("userName")
.verifyThat ()
.shouldBeDisplayed ()
.shouldBeEnabled ();```Need to solve issues found by Code Climate which can be found here.
Method buildCapabilities has a Cognitive Complexity of 10 (exceeds 5 allowed). Consider refactoring.
ServerSetting has 22 methods (exceeds 20 allowed). Consider refactoring.
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.