CrossBrowserTesting VS git-sizer

• Wide Range of Browsers and Devices
  CrossBrowserTesting offers a large selection of browsers and devices, allowing developers to test their applications in various environments to ensure compatibility.
• Live Testing
  Users can perform live interactive testing on real devices, enabling them to manually verify the behavior of their application and catch issues that automated tests might miss.
• Automated Testing Integration
  The platform provides integration with popular testing frameworks and tools such as Selenium, Appium, and others, facilitating automated testing workflows.
• Visual Testing
  CrossBrowserTesting offers visual testing capabilities, allowing users to compare screenshots from different browsers to identify design inconsistencies.
• Comprehensive Reports
  Detailed test reports with screenshots and logs are generated, helping users to quickly identify and address issues found during testing.
• Parallel Testing
  The service supports parallel testing, enabling users to run multiple tests simultaneously, significantly reducing the overall testing time.
• Easy-to-Use Interface
  The user interface is intuitive and user-friendly, making it easy for both beginners and experienced testers to navigate and utilize the platform effectively.

Possible disadvantages

• Cost
  CrossBrowserTesting can be expensive, especially for small teams or individual developers who might find the subscription plans to be cost-prohibitive.
• Performance
  Tests on real devices can sometimes be slow due to the availability and network constraints, which can affect the overall efficiency of the testing process.
• Limited Mobile Devices
  While the platform includes a variety of devices, the selection might not cover all the latest models or less common devices, potentially limiting testing coverage.
• Learning Curve for Advanced Features
  Some advanced features and integrations might require a learning curve, which could be challenging for users who are not familiar with automated testing or the specific tools supported.
• Test Timeout Issues
  Occasional issues with test timeouts have been reported, which can disrupt the testing process and require reruns or additional troubleshooting.

• Comprehensive Repository Analysis
  git-sizer analyzes many different dimensions of a Git repository including commit count, tree size, blob size, history depth, and reference counts, providing a holistic view of repository health and potential scaling issues.
• Easy to Use
  The tool is simple to run with minimal setup—just execute it within a git repository—and it produces clear, human-readable output that highlights potential problem areas without requiring complex configuration.
• Identifies Performance Bottlenecks
  It helps identify specific issues that could degrade Git performance, such as excessively large blobs, deep history, large trees, or too many references, which is valuable before migrating or scaling repositories.
• Open Source and Maintained by GitHub
  Being an official GitHub project, it benefits from credibility, community trust, and ongoing maintenance, and it is well documented with clear explanations of what each metric means.
• Useful for Pre-Migration Checks
  It's particularly helpful for teams migrating repositories to new platforms or consolidating repos, as it flags potential issues that could cause problems during migration or with hosting providers' limits.

Possible disadvantages

• No Automatic Remediation
  git-sizer only identifies and reports issues but does not offer any built-in tools or automated processes to fix problems like large blobs or excessive history depth—users must use separate tools like BFG Repo-Cleaner or git-filter-repo.
• Output Can Be Overwhelming for Beginners
  While detailed, the output includes many metrics and threshold levels that may be confusing for users unfamiliar with Git internals, requiring some learning curve to fully interpret results.
• Limited to Local Analysis
  The tool analyzes a local clone of the repository, so it requires users to have a full local copy of the repo (or at least enough history) to get accurate results, which can be time-consuming for very large repositories.
• No Real-Time Monitoring
  It functions as a one-time analysis tool rather than providing continuous or real-time monitoring of repository health, requiring manual reruns to track changes over time.
• Command-Line Only Interface
  The tool lacks a graphical user interface, which may be less accessible for users who prefer visual dashboards or are less comfortable with command-line tools.

Cross Browser Testing Tool Comparison – LambdaTest vs. CrossBrowserTesting

No git-sizer videos yet. You could help us improve this page by suggesting one.

• How can I test my site on safari if I don't have a Mac ?

  Yeah I moved on pretty quick from browserstack, but it seems to be the most popular. I've tried crossbrowsertesting.com but at the moment I really like app.lambdatest.com. Source: almost 4 years ago

• great list of "cool" sites from hnews

  Https://geizhals.de/ - this is a german site but the UI is nice and you can find a lot of stuff. Https://www.gsmarena.com/search.php3? - a phone search site. When I was at https://crossbrowsertesting.com we used this site a... - Source: dev.to / over 4 years ago

• Learn How To Create, Test and Deploy a Single Page App with Vue 3 + Vite and Pinia

  Fortunately we don’t need to install, nor configure, any other tools, unless maybe some fancy reporters, but for now we can get everything we need in terms of end-to-end automated testing out of Nightwatch. Besides Chrome, Nightwatch has... - Source: dev.to / over 4 years ago

View more

• how to keep github repos small?

  Also there’s a cool project from GitHub you can use to help understand the size of git’s objects in your git repo https://github.com/github/git-sizer. This might help you determine what the best cloning strategy could be. Source: almost 5 years ago