Below is the list of Challenges with Rest Assured:
Language Support: Support only Java Language.
Not Easy to learn: Implementation is not easy. Good Java knowledge required.
Performance Testing: Not integrated with tool.
Below are the challenges with PageFactory:
No of Pages: If there is an application with hundreds or thousands of web pages then the time and the effort in the development of automation framework will be high.
Maintenance Overhead: The cost increases when maintenance overhead increases which are due to the maintenance of large class as they break the OO design principle.
Programming Best Practices: The development of POM framework for multiple pages is equal to developers work thus testers should be highly knowledgeable in programming best practices.
Not Generic Model: Page object model is not a generic model and its specific to the applications.
The best approach to overcome the above challenges is by refactoring the POM concept to Screenplay Pattern.
Below are the different techniques:
Compression Techniques: Use JSON serializer and gZip compress techniques for the data transmitted over the web.
Use faster data access strategies
Caching: Have heard somewhere that the "fastest HTTP call is the one that you don't make" that is, use caching(Memcache/Redis), most of the requests are read operations, wise use of cache control headers are also useful. That spares the database from serving repeated read requests which are expensive. (Not sure if Etags can be of any use ?)
Use asynchronous methods judiciously
make as few API calls as possible
Programming level: use code optimization/threading/parallel programming.
Geography: Account for the distance between end users and origin servers, we can use CDNs for storing the static contents of the response, so that it can be served real fast.
API level: use pagination/filters/ranges to generate fine-grained data that is tailored to the need of the client.
Checked Exception: are the exceptions that are checked at compile time. If some code within a method throws a checked exception, then the method must either handle the exception or it must specify the exception using throws keyword.
Unchecked Exception: Unchecked are the exceptions that are not checked at compiled time.
Case 1: When Implicit Wait > Explicit Wait. For Example Implicit Wait is 60 seconds and Explicit Wait is 30 Seconds.
Then, Script will wait for 60 seconds.
Case 2: When Explicit Wait > Implicit Wait. For Example Implicit Wait is 20 seconds and Explicit Wait is 40 Seconds.
Then, Script will wait for 40 seconds.
Data provider returns a two-dimensional JAVA object to the test method and the test method, will invoke M times in a M*N type of object array. For example, if the DataProvider returns an array of 2*3 objects, the corresponding test case will be invoked 2 times with 3 parameters each time.
Example:
/**
* @return Object[][] where first column contains 'author'
* and second column contains 'Country'
*/
@DataProvider(name="SearchProvider")
public Object[][] getData()
{
return new Object[][]
{
{ "Ram", "India" },
{ "Sham", "UK" },
{ "Mohan", "USA" }
};
}
You can identify using access logs and check their Journey or Error from Mongo or any other logs.
The most common term for creating simulated components is mocking, but others are also used, and partly apply to different things; stubbing, simulation, and virtualization. The basic concept is the same - instead of using an actual software component (an API in our case) – a "replacement" version of that API is created and used instead. It behaves as the original API, but lacks many of the functional and non-functional characteristics of the original component. Which term is applicable depends on the degree to which the mock-up corresponds to the actual API:
Check below code:
package com.test.strings;
public class RemoveNumeric
{
public static void main(String args[])
{
String myString = "abc123def456";
System.out.println(myString.replaceAll("[0-9]", ""));
}
}
Output: abcdef
Copyright 2019. All rights reserved