Testing Archive - Bitwise https://www.bitwiseglobal.com/en-us/blog/tag/testing/ Technology Consulting and Data Management Services Fri, 29 Dec 2023 09:21:19 +0000 en-US hourly 1 https://cdn2.bitwiseglobal.com/bwglobalprod-cdn/2022/12/cropped-cropped-bitwise-favicon-32x32.png Testing Archive - Bitwise https://www.bitwiseglobal.com/en-us/blog/tag/testing/ 32 32 Delivering Results with Responsive UI Layout Test Automation https://www.bitwiseglobal.com/en-us/blog/delivering-results-with-responsive-ui-test-automation/ https://www.bitwiseglobal.com/en-us/blog/delivering-results-with-responsive-ui-test-automation/#respond Mon, 21 Aug 2017 07:07:00 +0000 https://www.bitwiseglobal.com/en-us/delivering-results-with-responsive-ui-test-automation/ What is a Responsive User Interface Responsive web pages are more user friendly than a single page which can be run only on a 1024 x 768 screen. A Responsive User Interface (UI) needs to self-adjust, or ‘respond’, according to various screen dimensions. This issue has raised the competition among various companies that need to ... Read more

The post Delivering Results with Responsive UI Layout Test Automation appeared first on Bitwise.

]]>

What is a Responsive User Interface

Responsive web pages are more user friendly than a single page which can be run only on a 1024 x 768 screen. A Responsive User Interface (UI) needs to self-adjust, or ‘respond’, according to various screen dimensions. This issue has raised the competition among various companies that need to represent their content in every way possible to deliver an optimal user experience no matter which devise is used.

A Responsive User Interface

Responsive web pages adjust themselves according to the device size, orientation, browsers and OS. Responsive design concepts reduce the struggle of how the user interacts with the content being delivered on the screen irrespective of the make of the device. Different frameworks use different dimensional methodologies to create responsive web pages. Hence, there is a need to create a generic set of automated layout tests which verify the layout of the page irrespective of the framework employed.

Indeed, the use of Responsive UI design has brought in the need to validate the UI layout on various viewports so that end user experience is properly tested before releasing the application.

Responsive UI Layout Testing Case Study

A perfect example of this need for Responsive UI Layout Testing comes from a recent project with one of our large enterprise customers in the Media sector. The customer was facing problems where its end users were unable to easily navigate to get access to content in the e-newspaper application due to its responsive nature. Users were experiencing issues with the content displaying properly on various viewports.

Challenges of Responsive UI Design and Testing

There were multiple challenges that needed to be addressed in order to provide a flawless user experience, including :

  • The daily e-newspaper was to be published with the UI showing news updates from various parts of North America, including content such as images and videos.
  • Advertisements needed to be properly visible in every dimension so that they could be clearly visible to the user, and the user should be able to click on the ads, enabling more ad revenue generation.
  • Menu Navigation for every page needed to be displayed properly on each device and orientation to enable accessibility.
  • Breaking news for the hour needed to be displayed as a footer.
  • Top news from every section needed to be visible with proper clicks to read the whole story.
  • Text needed to be fixed so as not to overlap at the edges with the decreasing size of the device.
  • Ability to flash correct error messages in case of any issues with good colors used to display the messages.
  • Images displayed needed to be of good quality and clearly visible.
  • Adjust alignment of text and images with change in orientation and screen size.
  • Change colors on hovering the mouse over necessary buttons and links.
  • Needed a good content consumption environment which followed the rule “follow users not devices.”
  • All the above mentioned criteria needed to be tested for every page along with the regression testing in case of some changes as there needed to be innovation and creativity in the design.

Ultimately, the customer needed a solution that could help make its product more optimized to enrich the end user experience, as well as make its content easily visible with varying screen sizes over different devices with optimum accessibility. This also meant that advertisements placed on the content needed to be properly validated so that there is no loss of revenue leading to stakeholder dissatisfaction.

Automated Responsive UI Layout Testing Solution

The Bitwise QA Center of Excellence took up the challenge by first chalking out the Layout Testing Automation solution. The team’s approach included the following steps, and the solution delivered was aligned with best practices :

  • Analyzing the pages with the most critical content.
  • Defining the viewports (Browser / Device) on which the UI needs to be validated.
  • Using open source API (Galen) and creation of various gspec files, which essentially include layout tests, ensuring best practices are followed.
  • Writing user interactions using Selenium WebDriver in the tests.
  • Use of single tests for both Browser and Mobile devices (Android and iOS).
  • Executing these tests on Cloud Devices (Android and iOS) and Browsers.
  • Reporting automated test results through emails to stakeholders.

Automated Responsive UI Layout Testing

The approach ensured that CB (Cross-Browser) and CD (Cross-Device) Testing was aided using a cloud solution coupled with an open source API to ensure optimum test coverage. These tests were then executed periodically during regression.

This resulted in ensuring that the content and elements on the pages are displayed flawlessly over various viewports. As a result, the test suite created added value to regression testing by optimally validating the UI on various layouts after changes were done to the applications.

Increased Customer Satisfaction

Bitwise provided a complete automated responsive UI test solution that received enormously positive feedback from its users, leading to a 40% increase in ad revenues. In addition, the subscription rate increased due to the efficacious automated testing provided by our test suite design.

With our expertise in delivering solutions around Responsive UI Layout Test Automation, we set up a framework using open source tools and APIs. As a result of using our test suite to identify issues on various viewports and OS, the customer achieved ROI in terms of better quality and content leading to increased customer satisfaction. The test suites created were generic and easily maintainable, which also reduced maintenance costs and served as a cost saver during the long run.

What challenges are you facing in designing and testing your Responsive UI Layout? Leave a comment below or contact Bitwise…we’d love to help.

The post Delivering Results with Responsive UI Layout Test Automation appeared first on Bitwise.

]]>
https://www.bitwiseglobal.com/en-us/blog/delivering-results-with-responsive-ui-test-automation/feed/ 0
Functional Test Automation (Mobile & Web Services) https://www.bitwiseglobal.com/en-us/solution-summary/functional-test-automation-mobile-web-services/ https://www.bitwiseglobal.com/en-us/solution-summary/functional-test-automation-mobile-web-services/#respond Tue, 16 Aug 2016 00:00:00 +0000 https://www.bitwiseglobal.com/en-us/solution-summary/functional-test-automation-mobile-web-services/ The key to successfully implementing a Test Automation solution is overcoming the impending challenges (i.e., requirements capturing, selecting the right tools, honing the skillsets of QAs, and proper enhancement of regression suite and maintenance). Bitwise understands these challenges, and has placed prominent markers in place to ensure that maximum ROI is achieved through Test Automation. ... Read more

The post Functional Test Automation (Mobile & Web Services) appeared first on Bitwise.

]]>
The key to successfully implementing a Test Automation solution is overcoming the impending challenges (i.e., requirements capturing, selecting the right tools, honing the skillsets of QAs, and proper enhancement of regression suite and maintenance). Bitwise understands these challenges, and has placed prominent markers in place to ensure that maximum ROI is achieved through Test Automation.

Key Features

  • Holistic feasibility study to analyze automation before the deep dive
  • Test Automation Frameworks (Keyword, Data, and Hybrid) which can be reused for different Web and mobile applications (Native, Hybrid, and Web)
  • Reduction in Testware development time and effective maintenance
  • Testing with Cloud-based tools to enhance test efficiency and reducing Testware development time
  • Cloud-based testing on a variety of browsers for Web and devices for Mobile apps, with a variation in operating systems providing efficient coverage of real-usage scenarios
  • Responsive UI layout testing on a wide range of browsers and devices
  • Acceptance Test Automation using behavior-driven development tools
  • Proven experience in test automation regression maintenance

Key Benefits

  • Exploitation of Open Source tools/APIs to generate cost effectiveness
  • Reduction in time to market and effective ROI
  • Adherence to best practices and best QA tools available
  • Skilled QA staff
  • Tailor efficient test automation solutions using Open Source and/or licensed tools
  • Yields higher Automation Index (higher % of automated test cases)
  • Per the points above we were able to get an Automation Index of close to 82% for a Fortune 500 client and hence increased the ROI by Test Automation
  • Proven substantial difference achieved for cost comparison between manual testing efforts and automation efforts

Service Oriented Architecture (SOA) Testing

Web services are key to the success of any distributed business with a vast expanse of products/services. Hence, the need of developing and testing Web services to allow cross-platform integration and proper business flow from one domain to another becomes important. Bitwise has vast experience handling such complex testing scenarios through years of creating efficient testing solutions for many of our Fortune 500 clients.

Key Features

  • Expertise in testing SOA with SOAP and RESTful Web services
  • Use of virtualization to address Shift-Left testing before interim blocks are developed
  • Usage of market-leading licensed and Open Source tools
  • Expertise in middleware migration and testing
  • Testing with various middleware and scripting to customize the test cases

Key Benefits

  • Thoroughly conversant with challenges in Web service testing
  • End-to-end testing of Web services using Open Source tools/APIs
  • Through insights into complex virtualization and testing tools
  • Testing solution encompasses performance and security testing
  • Minimal test setup and faster ROI
  • Following Criticality Metric to ensure all the critical components of SOA are placed along the Test Bed for testing
  • Excellent test coverage

 Improve the performance of your IT systems, speed time to market and curtail your software testing cost. Click here to know more.

[contact-form-7]

The post Functional Test Automation (Mobile & Web Services) appeared first on Bitwise.

]]>
https://www.bitwiseglobal.com/en-us/solution-summary/functional-test-automation-mobile-web-services/feed/ 0
Shift-Left Testing and Overall Quality https://www.bitwiseglobal.com/en-us/blog/shift-left-testing-and-overall-quality/ https://www.bitwiseglobal.com/en-us/blog/shift-left-testing-and-overall-quality/#respond Mon, 24 Aug 2015 14:17:00 +0000 https://www.bitwiseglobal.com/en-us/shift-left-testing-and-overall-quality/ Shift-left testing Doing away with all the traditional paradigms of software development, shift left testing stresses integrating both key activities (development and quality assurance) from day one of the projects. This promotes the inclusion of quality assurance right from the requirement phase of development and carries down to the other phases as they follow. SQSPer ... Read more

The post Shift-Left Testing and Overall Quality appeared first on Bitwise.

]]>

Shift-left testing

Doing away with all the traditional paradigms of software development, shift left testing stresses integrating both key activities (development and quality assurance) from day one of the projects.

This promotes the inclusion of quality assurance right from the requirement phase of development and carries down to the other phases as they follow.

SQSPer a study conducted by SQS, 56% of defects originate during the requirement phase of the project as compared to a meager 7% during the coding phase.

blog-sqs

Per the traditional models, testing starts when development is in the coding phase.

This would essentially mean that most of the testing activity targets the wrong phase of development, missing 56% of the defects.

There is a remote possibility that these defects are discovered during the rest of the testing. If they are discovered, this would mean improving the quality of already degraded software.

The shift-left model accelerates the attention to quality from the inception of the project.

This increases the ability to discover and correct defects when they occur.

As shown below, testing manifests right from the start of the project and carries down to the end of the project.

The main activity of testing revolves around the basic inception phases. Therefore, defects caught at this point are easy to fix and not costly.

blog-sqs-chart

Finding a defect during the ‘typical’ testing phase can mean more than 15 times the cost to fix and countless hours of unnecessary re-work.

With the shift-left model, the focus on quality becomes everyone’s priority and with less re-work, projects stay truer to timelines and estimates.

Another benefit is that it improves cost-effectiveness and ensures a faster time to market.

The use of shift-left testing yields the following benefits

  • Bugs are found and fixed early
  • Saving time and resources
  • Allowing good test coverage
  • Better teamwork with developers and testers – this model minimizes frictional differences between them
  • Delivery of software is expedited
  • Cost-effectiveness

If you need a solution to your quality, cost, and time woes, contact Bitwise and see how we can help.

The post Shift-Left Testing and Overall Quality appeared first on Bitwise.

]]>
https://www.bitwiseglobal.com/en-us/blog/shift-left-testing-and-overall-quality/feed/ 0
How To Conduct Effective Testing Of Business Intelligence Applications https://www.bitwiseglobal.com/en-us/blog/how-to-conduct-effective-testing-of-business-intelligence-applications/ https://www.bitwiseglobal.com/en-us/blog/how-to-conduct-effective-testing-of-business-intelligence-applications/#respond Mon, 24 Aug 2015 13:04:00 +0000 https://www.bitwiseglobal.com/en-us/how-to-conduct-effective-testing-of-business-intelligence-applications/ BI Testing Strategy The goal of testing BI applications is to achieve credible data. And data credibility can be attained by making the testing cycle effective. A comprehensive test strategy is the stepping stone of an effective test cycle.   The strategy should cover test planning for each stage, every time the data moves and state ... Read more

The post How To Conduct Effective Testing Of Business Intelligence Applications appeared first on Bitwise.

]]>

BI Testing Strategy

The goal of testing BI applications is to achieve credible data. And data credibility can be attained by making the testing cycle effective.

A comprehensive test strategy is the stepping stone of an effective test cycle.   The strategy should cover test planning for each stage, every time the data moves and state the responsibilities of each stakeholder e.g. business analysts, infrastructure team, QA team, DBA’s, Developers and Business Users.  To ensure testing readiness from all aspects the key areas the strategy should focus on are:

  • Scope of testing: Describe testing techniques and types to be used.
  • Test environment set up.
  • Test Data Availability: It is recommended to have production like data covering all/critical business scenarios.
  • Data quality and performance acceptance criteria.

The below diagram depicts the data entry points and lists a few sample checks at each stage. – Data Collection, Data Integration, Data Storage and Data Presentation.

data-entry-points

Data Acquisition

The primary aim of data completeness is to ensure that all of the data is extracted that needs to be loaded in the target.  During the data acquisition phase it is important to understand the various data sources, the time boundaries of the data selected and any other special cases that need to be considered.  The key areas this phase should focus on are:

  • Validating the data required and the availability of the data sources from which this data needs to be extracted.
  • Data profiling:  Embedding data profiling activity helps in understanding the data, especially identifying different data values, boundary value conditions or any data issues at early stages.  Identifying data problems early on will considerably reduce the cost of fixing it later in the development cycle.

Data Integration

Testing within the data integration phase is the crux as data transformation takes place at this stage.  Business requirements get translated into transformation logic.  Once the data is transformed, thorough testing needs to be executed to ensure underlying data complies with the expected transformation logic.  Key areas this phase should focus on are:

  • Validating the Data Model: This involves validating the data structure with business specifications.  This can be done by comparing columns and their data types with business specifications and reporting column requirements ensuring data coverage at source.
  • Reviewing the Data Dictionary: Verifying metadata which includes constraints like Nulls, Default Values, Primary Keys, Check Constraints, Referential Integrity, Surrogate keys, Cardinality (1:1, m: n), etc.
  • Validating the Source to Target Mapping:  Ensuring traceability throughout will help build the quality aspects like consistency, accuracy and reliability.

Data Storage

The data storage phase refers to loading of data within the data warehouse/data mart or OLAP cubes.  The data loads can be one time, incrementally or in real-time. Key areas this phase should focus on are:

  • Validating data loads based on time intervals.
  • Performance and Scalability: Testing of initial and subsequent loads with performance and scalability aspect ensures that the system is within acceptable performance limits and can sustain further data growth.
  • Parallel Execution and Precedence: Verifying appropriate parallel execution and precedence during ETL process is important as it may impact directly on performance and scalability of the system.
  • Validating the Archival and Purge Policy: Ensures data history based on business requirements.
  • Verifying error logging, exception handling and recovery from failure points.

Data Presentation

This is the final step of the testing cycle and has the privilege of having a graphical interface to test the data.  Key areas this phase should focus on are:

  • Validating the Report Model.
  • Report layout validation as per mockups and data validation as per business requirements.
  • End to End Testing:  Although individual components of the data warehouse may be behaving as expected, there is no guarantee that the entire system will behave the same.  Thus execution and validation of end-to-end runs are recommended.  Along with data reconciliation discrepancies, issues might surface such as resource contention or deadlocks. The end-to-end runs will further help in ensuring the data quality and performance acceptance criteria are met.
dw-bi-testing-best-practices1

While above considerations are given, one important aspect that still remains to be addressed is the issue of ‘Time’.  BitWise has created a platform based on DW/BI Testing Best Practices that automates and improves the overall effectiveness of DW/BI Testing. If you’re interested in learning more about this platform, please contact us.

With the features and benefits of this platform, the intention is to address most of the DW/BI testing challenges:

  • End-to-end traceability achieved right through source extraction to reports.
  • 100% requirement and test data coverage through test cases.
  • Test case automation of standard checks achieving considerable time savings.
  • Up to 50% time savings through automated regression testing.
  • Defect or bug tracking involving all the stakeholders.
  • Improved testing cycle time through reusability.
  • Process improvements with analytical reporting showcasing test data, test cases & defect trends.

Conclusion:

Testing BI applications is different than testing traditional enterprise applications.  To achieve truly credible data, each stage of the lifecycle must be tested effectively – Data Collection, Data Integration, Data Storage and Data Presentation. If you’re not comfortable with your internal capabilities to test your BI applications, turn to the BitWise DW/BI Testing platform and lean on BitWise’s expertise and experience gained through testing business intelligence applications for clients over the past decade.

The post How To Conduct Effective Testing Of Business Intelligence Applications appeared first on Bitwise.

]]>
https://www.bitwiseglobal.com/en-us/blog/how-to-conduct-effective-testing-of-business-intelligence-applications/feed/ 0
Mobile App Testing Is Not The Same As Desktop App Testing https://www.bitwiseglobal.com/en-us/blog/mobile-app-testing-is-not-the-same-as-desktop-app-testing/ https://www.bitwiseglobal.com/en-us/blog/mobile-app-testing-is-not-the-same-as-desktop-app-testing/#respond Mon, 24 Aug 2015 12:06:00 +0000 https://www.bitwiseglobal.com/en-us/mobile-app-testing-is-not-the-same-as-desktop-app-testing/ The Strategy Apps developed by the company included Web Apps, Native Apps and Hybrid Apps. Jeff took stock of all the technology and testing methodologies and was confident that he would crack the deal for an Automotive Service Giant, where he was to first deliver his premier sales presentation for an App that the company ... Read more

The post Mobile App Testing Is Not The Same As Desktop App Testing appeared first on Bitwise.

]]>

The Strategy

Apps developed by the company included Web Apps, Native Apps and Hybrid Apps. Jeff took stock of all the technology and testing methodologies and was confident that he would crack the deal for an Automotive Service Giant, where he was to first deliver his premier sales presentation for an App that the company had developed for such business models.

The Mobile App

The App was built on Jelly Bean Android Platform Version 4.3 specifically designed for Car Service Center chains across North America and Canada.

The App would help the Supervisors and the Technicians working at the Service Center make informed decisions while routing the car owners to a particular Service Station within 4 miles in case that the car bay at any given Station was at full capacity. This situation would mostly happen over weekends and the customers would experience long wait times to get their cars fixed or serviced. The App would also correctly route customers to stores based on the availability of parts.

The App would provide a benefit to the client – effectively manage the inflow over weekends and would also improve Customer Satisfaction, which in turn would positively impact the bottom line of the business. It was tested thoroughly and a limited-feature version was put on the Android Play Store available as a FREE download.

The Presentation

Jeff flew to Orlando, FL to present the App at the Car Service Company. This deal would be a milestone for his company if it was cracked.

Jeff was to present the salient features of the App to the top brass of the company which included 12 people across the different verticals of the organization. He started his presentation with his Android device connected to a device projector.

He ruled the roost when it came to presenting the App and the value it would add to the company. Soon everyone was impressed and the work seemed done before he even closed on the presentation to solicit any queries. He was standing on the podium with confidence until…..

The Bug

A rather amplified voice from the Manager of Services asked Jeff whether he could download the same App to his Android device. Jeff smiled and gave him the instructions to download. The Manager became busy with his mobile device for some time and soon he found out that he was unable to download the App on his device and every time he would do so, he would get an error:
“<insert app name >” could not be downloaded due to an error. (403)

After a couple of attempts in vain, he raised his voice yet again “it just won’t get on my phone”. Everyone in the board room seemed curious about what was going on. Jeff was left with no answer and he was just beating around the bush handling queries. Then someone from the team suggested to try downloading the App on WIFI without using the Carrier provided Network.

That worked and the App downloaded in a flash. But it would not work on the Carrier provided network. There it was, “A BUG”, everything seemed so well if this nasty bug had not surfaced. Skepticism overruled optimism and it all came to a grinding halt!

The Retrospection: Autopsy of Disaster

Jeff‘s disappointment slowly transformed into a thorough retrospection during the long trip back to the pavilion. “Why was this not tested?” was the question that was hitting the neurons of his brain again and again. “What’s going on? We are a service-based company with a special focus on Products, how could such a thing happen?”

Jeff’s retrospection uncovered that the QAs were accustomed to testing their Apps only on a selection of devices, but carriers required more money for procurement. It was not long before Jeff realized that Mobile Testing was completely different compared to Desktop Testing.

At BitWise, we understand this. Our Mobile App Testing approach focuses on covering the following salient features:

  • Crowd-Sourced Testing: Accommodate the need of a wide array of devices and different carriers to cover testing the app on all the possible hardware combinations
  • Performance Testing: Mobile Apps NEED to be tested on various Networks such as 3G, 3G+, H+, and 4G LTE
  • Mobile App Battery Consumption Testing: Usage of Freeware tools to analyze the battery consumption by an App on a device.
  • Automated Testing: Stress the use of Automation testing but the main challenge in Automation is technicality and Cost of the Tools. Cloud-based tools which provide a gamut of devices on various carriers also require technical knowledge but as far as the Cost is concerned; such tools are at times out of budget for many organizations.

The Out of the Box Solution: Automation

To beat this budget problem, BitWise has come up with a clever combination of testing strategies based on various cloud-based mobile testing providers with complementary strengths. Apart from reducing the cost, the user gets a multitude of choices for mobile platforms and carriers. Best of both worlds!

Conclusion:

Want to know what Jeff did at the end of his retrospection? He called us. The cloud-based mobile testing strategy that BitWise formulated for him, has enabled him to overcome his original testing woes. His mobile app meanwhile continues to add new happy customers every day.

Mobile App Testing approached with a different perspective, has resulted in efficacy, efficiency, and cost-effectiveness.

Does Jeff’s story ring a bell? We need to talk. Let us know how we can help.

The post Mobile App Testing Is Not The Same As Desktop App Testing appeared first on Bitwise.

]]>
https://www.bitwiseglobal.com/en-us/blog/mobile-app-testing-is-not-the-same-as-desktop-app-testing/feed/ 0