Fichas
Mobile & Misc
Fichas del conjunto (63)
- 1Native appscreated for use on a platform like mobile and tablets (created to run locally)
- 2Mobile web apps:server side apps to access website/s on mobile using different browsers like Chrome, Firefox by connecting to a mobile network or wireless network like WIFI
- 3Hybrid appsare combinations of native app and web app. They run on devices or offline and are written using web technologies (works over the network, nothing is stored locally)
- 4How to test ? (in ADDITION TO STLC) 1. Identify and plan⦁ Os and their versions
⦁ Internal Hardware
⦁ Network
⦁ Screen sizes and resolution etc. - 5How to test ? (in ADDITION TO STLC) 2. Build Environment⦁ Set an internal mobile lab or plan for mobile cloud provider (what system we are testing & what are the differences)
- 6How to test ? (in ADDITION TO STLC) 3. Execution⦁ Execute test cases on the defined set of environment
- 7How to test ? (in ADDITION TO STLC) 4. Reporting⦁ Report the bugs
⦁ Fix the Defects
⦁ Re-test to confirm defect fixing - 8Testing TypesCompatibility testing
Installation testing
Interruption testing
Performance Testing - 9Compatibility testingis to ensure whether different software is compatible with different configurations and whether the application is compatible with the client's environment.
- 10Installation testingof testing that is done at the initial stage of mobile app life span
checks whether the mobile app installs, uninstalls and updates propely without any interruption.
first impression on the users - 11Interruption testingInterrupt testing is a process to replicate abrupt (Unexpected) interrupt to the application
done to understand how the app behaves under certain interruptions before resuming to its original state. - 12Performance Testingto test the performance of the mobile application in expected working scenarios and to eliminate the performance hurdles
checks whether the response of the application is quick, the ability of the app to take load and stability of those load situations. - 13Usability Testingof testing which is performed to check how user-friendly the mobile application is in terms of the navigation, ease to use the app, flexible app controls, etc.
- 14Generic Interrupts(test cases) for ex: battery removal
- 15critical interruptsassesing the application components and architecture( for ex: is the app using GPS?)
- 16Map the interrupts with application state(test cases) for ex: network interrupts during transition after payment submit
- 17repository urlclone link (github copy button)
- 18root pompom xml
- 19cucumber.filter.tags = "@Smoke"will look for all feature files with @Smoke annotation
- 20docker containerclean enviroment, with all needed / relevant tools, optimized to run just those, nothing extra
created on demand for test execution, after each test execution current docker container is removed - 21virtual machineapplication that allows you to open another operating system inside another (like BrowserStack, emulates mobile environment)
- 22docker setupour devops helps us set up jenkins and mapping our framework to docker containers
- 23RestAssuredAPI automation using postman then writing code via RestAssured library
- 24jmeterused for automating API test, also used for mass update of data of configurations for your system (in case you need to perform for ex: 5k trades, selenium takes time, jmeter 5mins)
- 25what can we set in jenkins?we can usually set: branch we are running, and maybe repository (rest set by devops)
- 26CSVcomma separated value file is a simple text file in which information is separated by commas, and is common in spreadsheet apps. Each line of the file is a data record.
- 27Zeppelin / FigmaApplication for UI Designers
- 28Interfaceany way of interaction
- 29Confluencedefers a single point of failure, and creates transparency between team/s
- 30jawstool built for accessibility testing for govt project
- 31web app vs mobile in testingWeb applications has more features, also for automation you can make same code work for both mobile and webbased using React Native
- 32do we need to test on all mobile devices?You don't need to test on all mobile devices, only one that represents that particular family
- 33Where do we collect statistics?mobile - app store
web - browser - 34Test Case Integration Toolstestrail (easier to intergrate w/ automation)
Zephyr(integrateable w/ jira)
Practitest (easier to manage) - 35smoke testingto check the most critical aspects of the application, making sure its stable
- 36BrowerStackonline tool that allows us to simulate diff devices (cross browser, cross os, good for WEB Testing ONLY)
- 37Kobitonlike BrowerStack (but can install our app (native & web) on the device)
it is intergratable with current automation framework
allows mobile testing using IntelliJidea, using selenium like libraries (Epium) (without installing additional addons) - 38Simulatingnot reproducing device, it just looks like it on a pc screen (UI Only & size)
- 39Emulatingreproducing the core function & most of functions of that device
- 40Can part of the test code used both for web & mobile apps?Yes, Part of the code can be used for both mobile & web apps
- 41cucumber keywords: BEFOREwill run the code that is following that annotation before each test / gherkin scenario outline
- 42cucumber keywords: AFTER-will run the code that is following that annotation after each test / gherkin scenario outline
- 43cucumber keywords: SCENARIOThe keyword Scenario is a synonym of the keyword Example.
You can have as many steps as you like, but we recommend 3-5 steps per example. Having too many steps will cause the example to lose its expressive power as a specification and documentation. - 44cucumber keywords: ANDused to add another event or action
- 45cucumber keywords: THENsteps are used to describe an expected outcome, or result.
- 46cucumber keywords: WHENused to describe an event, or an action. This can be a person interacting with the system, or it can be an event triggered by another system.
- 47cucumber keywords: GIVENsteps are used to describe the initial context of the system - the scene of the scenario. It is typically something that happened in the past.
- 48Cucumber framework setup: pre condition- setting up browser, setting up some dependencies / instances / objects if needed
- 49Cucumber framework setup: post conditionis removing the browser and clearing
- 50maintenance of test coderefactoring, updating locators
- 51feature files recommended to be1 per test method , for it to be more structurally sound
- 52APIApplication Programming Interface - specific HTTP channels that are connecting front & back end allowing you to transfer data
- 53when we perform API Testing we arechecking the response code
checking and matching required json if put / delete request - 54response code 100informational
- 55response code 200successful request
- 56response code 300redirected
- 57response code 400something wrong with front end
- 58response code 500something wrong with back end
- 59XMLA file with the .xml file extension is an Extensible Markup Language (XML) file. These are really just plain text files that use custom tags to describe the structure and other features of the document.
(can see in POM.xml file) , - 60JSON(very plain) has key value pairs, like a complex hashmap, parent > child structure
- 614 types of API requests we performget - get info
post - post info
delete - request the deletion of info (data payload - instruct what element / data should be removed)
put - update (data payload - instruct what element / data should be updated) - 62most popular Response Headerscontent type,
user-agent (containing info) - 63what does jenkins do?pulls the code from github and sends it to some remote server or remote machine
Información
- Descripción
- QA Engineer Mobile Testing Fichas sobre Mobile & Misc, creado por Mircea Manu el 27/01/2022.
- Creado por
- Mircea Manu
- Visitas
- 1
- Valoración