Cloud Testing

Hi folks,

Few things on cloud testing

 Cloud testing type

• System testing
• Interoperability testing – infrastructure
• Performance
• Availability
• Multi tenancy- security
• Disaster recover

 

Cloud testing key objectives

• Ensure excellence of cloud based applications
• Authenticate software as service in cloud environments
• Verify automatic cloud based functional service
• Analyze inter operation capabilities and compitability

 

Consideration for cloud based testing APIs

• Data security and privacy
• Data migration
• Interface compitability
• Enterprise application integration

 

Cloud Test environment types

• Cloud based enterprise test environment
• Private/public test environment
• Hybrid cloud test environment

 

Challenges of cloud testing

• Lack of environment control
• Lack of transparency
• Query limitation
• Self modification and autonomic behavior
• Asynchronous interaction
• Time and load dependent behavior
• Huge configuration space
• Ultra large scale
• Low observity

 

Challenge SAAS with dummy data

Place holder of simultate the real data with no impact

• Simulate behavior of real data
• Can be quickly created to test API
• Allow developer to focus on test

Role of dummy data in test API

• Nominally occupy space of real data
• Act as stub to avoid api testing issue
• Data for security testing

 

Cloud testing benefits

• Flexible, comprehensive and indicative testing
• Reduce cost of ownership
• Promote green IT
• Geographic transparency and traceability

 

Cloud testing strategy

• Stress- testing till breaking point
• Performance- measure response time
• Functional
• Latency
• Security 
• Capacity testing= max capacity for current future hardware
• Governance risk compliance test
• Load- system stability

 

Service model as Test as a servie (TAAS)

• Taas process management
• Access TAAS  service
• On demand test environment
• Service option
• Service provisioning
• Service execution

 

TAAS benefit

• Reduce cycle time
• Reduce business risk
• Improve agility with highly automated solutions
• Helps leverage transactional pricing model for predictable and affordable solutions

 

TAAS provider- IBM, SOASTA, sauselab,skytap,vmlogics,

Code Review Checklist

 Hi Folks,

Follow below code review checklist

Sr. No    Checklist Item   Category

1            Use Meaningful Names and camelcaseletters for variables and method names Readability

2            Add Proper Comments for your Code     Readabilty/Maintanance

3            Avoid Duplication of variables and methods        Reusability

4            Donot write in single line             Readability

5            Avoid creating unnecessary objects         Performance

6            Remove Unwanted Imports        Standards

7            Make sure the code formatting is applied            Standards

8            Make sure the code meets the functional requirements              Functionality

9            Check side effects on existing codes if any modification in script              Functionality

10          Make sure to do clean up for unwanted code      Standards

11          Limit the accessibility of packages,classesand methods only to necessary places             Accessiblity

12          Donot expose confidential Data in logs   Security

13          Make sure the exceptions are handled   Exceptions

14          Avoid excessive logs       Standards

15          Avoid Multiple If cases   Performance

16          Try using dynamnic waits (Avoid Thread sleeps) Performance

17          Avoid Hardcoded values in code Security

18          Free up space/Memory after use             Performance

19          Minimize the scope of local variables      Accessiblity

20          Exceptions should be Throwable              Exceptions

21          In every catch statement – call the UI reusable library function and catch block should not be empty              Reusability

22          Try to avoid use of mobile center in condition     Standards

23          use appropriate hard assert for the mandatory validation               Standards

24          Assertion should be use outside the try catch block and in case needed to use in try block than Catch(AssertionError e) should handle correctly             Standards

25          Xpath: There should not be any platform specific xpath hardcode in the code/pageclass        Standards

26          Xpath should not be directly written in methods .Write only in Page factory  Readabilty/Maintanance

27          Xpath- use only absolute xpaths Standards

28          xpath- do not use ID in xpaths    Standards

29          xpath- use dynemic index instead of hardcoding in xpath              Standards

30          There should be no test data pass through any of the property files              Security

31          Any test data input should be from Excel              Security

32          Nowhere Environment details should be hardcoded for any kind of validation           Security

33          Always use the 3/2 argument Assert statement for code readability point of view (expected/actual/description of validation)              Readability

34          Device type should handle via object repository only. Device type should not written in class files  Maintanence

35          All public method should be on top of the class and all private method should be below it          Readability

36          There is no hard of validation message in page classes, it should be in validation message file            Reusability

37          All feature file should have tag with particular UB number              Standards

38          Reporting- all the necessary validation should be part of reporting along with screenshots  Standards

39          Reporting- all the reporting verbage should be proper along with appended test data for validation for actual vs expected Standards

40          Reporting-Use reusable reporting function for screenshot, allure and extent reporting      Readability

41          Reporting- Keep only screenshot option to Yes, if needed else switch of the function    Performance

42          Reporting- Take screenshot of entire page at least once during the validation journey           Readability

Drivers for tool selection

 Drivers for tool selection

1.lower opex

2. Faster payback/break even

3. Faster script build

4. Faster script run -execution and maintenance 

5. Most technology supported

6. Better % automation

7. Easier to skill

8. Faster to scale

9. Easier end to end automation

10. No manual script creation

11. Industrialisation of testing

Digital Transformation Benefits

 Benefits of digital transformation

1. Cost reduction

2. Improve worker productivity 

3. Improve customer experience 

4. Regulatory compliance 

5. Accelerate digital business transformation 

Cheers

TJ