Xam expertday

Xam expertday

• 1.
  #XamExpertDay
• 2.
  UI Testing with Xamarin.Forms CodrinaMerigo _Codrina_
• 4.
  WHY
• 6.
  Unit Tests arenormally written by the developers who write test code to verify the functionalities that were developed by them. Picture credits : https://mobilefirstcloudfirst.net/wp-content/uploads/2017/01/Test-Pyramid-1024x806.png UI Tests This is the layer where you would be testing the product more from an end-user’s perspective. Your top priority would be to ensure that ‘UI Design Flow’ is in-line with the design requirements. App Testing Since the testing at UI level is so brittle, it is recommended to focus on these tests to only verify ‘UI flow & interactions’ without looking into the system functionality. Service Tests helps you ensure that the services are working properly and give you the right data.
• 7.
  Fast (ui testsare slow but dev must try not to write them even slower) Independent(not use other tests) Repeatable (not use constants like access tokens) Self-validating(by using asserts) Timely ( try not to be very complicated, maybe an action can be split in multiple tests). F.I.R.S.T. Principles
• 8.
  UI Test Project if(platform == Platform.Android) { return ConfigureApp.Android .EnableLocalScreenshots() .DeviceSerial(DroidDeviceID) .Debug() .ApkFile(ApkPath) .StartApp(); } else return ConfigureApp.iOS .EnableLocalScreenshots() .Debug() .DeviceIdentifier(IOSDeviceID) .AppBundle(AppPath) .StartApp(); To find the ios device id run instruments -s devices on your mac, for android launch adb devices from command line ApkPath is something like "C:UsersProjectsMyAppMyApp.AndroidbinDebugmyApp.apk" AppAPath for the ipa is something like ="../../../MyApp/MyApp.iOS/bin/iPhoneSimulator/Debug/MyApp.iOS.app"
• 9.
  Repl() - read-eval-print-loop TheREPL is a console-like environment in which the developer enters expressions or commands. It will then evaluate those expressions and display the results to the user. The REPL is helpful when creating UITests as it allows us to explore the user interface and create the queries and statements so that the test may interact with the application. tree app.Query(e => e.All())
• 10.
  DEMO
• 11.
  Sample Arrange, Act, Assert publicint MySum(int a, int b) { return a + b; } [Test] public void TestMySum() { // Arrange int a = 5; int b = 7; // Act int result = MySum(a, b); // Assert Assert.AreEqual(12, result); } AAA Pattern
• 12.
  This process allowsyou to write tests a non-technical language that everyone can understand (e.g. a domain-specific language like Gherkin). BDD forms an approach for building a shared understanding on what kind of software to build by discussing examples. Behavior Driven Development BDD Approach Given When Then As a [role] I want [feature] So that [benefit] As a registered user, I want to be able to login, so that I can see the Application. Scenario 1: User is able to log in. Given that I am a registered user, when I enter the username ‘Codrina’ and password ‘ladybug’, then I should see the first screen of the app. Sample
• 13.
  In order toidentify a control on the screen, each control needs an unique identifier called AutomationId set to the visual element, for example: <Label x:Name="label1" AutomationId="MyLabel" Text="Hello, Xamarin.Forms!" /> Or var label1 = new Label { Text = "Hello, Xamarin.Forms!", AutomationId = "MyLabel" }; AutomationId – your new best friend UI Automation is supposed to run slow in order to emulate an actual user interaction - keep that in mind that sometimes we may wait for an element to pop on the screen before we verify if it is actually on the screen. It’s important also to write every single action and not take anything for granted
• 14.
  DEMO
• 15.
  Queries inside andoutside Repl() Samples //label bool myLabel = app.Query(e => e.Marked(“MyLabel")).Any(); app.Tap(“MyLabel"); //syncfusion element switches = app.Query(e => e.Marked("SfSwitch Control. State changed")); x = (float)switches[c].Rect.CenterX; y = (float)switches[c].Rect.CenterY; app.TapCoordinates(x, y); //swipe gestures app.SwipeLeftToRight(); //entry app.Tap(“MyEntry"); app.EnterText(Constants.Value); app.DismissKeyboard(); //inside webview /*through Safari for iOS and through Chrome for Android use the browser developer tools to visually identify the elements inside the DOM.*/ app.Tap(c => c.WebView().Css("#element"));
• 16.
  DEMO
• 17.
  Run your testson App Center Test Cloud appCenter Validation Upload package and UI Test using nodeJs and following app center instruction Wait for devices Run on first device when ready Run on second device when ready Run on nth device when ready Configure your run by selecting Generate report for results Run on third device when ready
• 18.
  App Center TestCloud Reports
• 19.
  Add Ui Teststo DevOps using AppCenter From app center you get: appcenter test run uitest --app "codrinamerigo/LadyBug" --devices "codrinamerigo/android-test" --app-path pathToFile.apk --test-series "master" --locale "en_US" --build-dir pathToUITestBuildDir Enable task
• 20.
  Add Ui Teststo your TFS mono ../../../NUnit.Runners.2.6.3/tools/nunit-console.exe myApp/MyApp.UITest/bin/Debug/ myApp.UITest.dll -xml=UITestResult.xml TFS NUNIT
• 21.
  If sometimes, theiOS simulator doesn’t pop on the screen, might be useful to delete the xdb folder inside TMPDIR (on the Mac machine) and retry. For debug purpose, right-click on the iOS Project > Options > Compiler and add the string ENABLE_TEST_CLOUD Try to write no more that 20 ui tests per project to run them locally… Open the Android simulator on your Mac before running the tests Don’t forget about your UI Test – try to keep them live UI Tests aren't compatible with the Shared Mono Runtime, so remember to disable it for Android! From myexperience . . .
• 22.
  Q & A
• 23.
  Thank You! _Codrina_