inav VS paparazzi

Compare inav vs paparazzi and see what are their differences.

paparazzi

Render your Android screens without a physical device or emulator (by cashapp)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
inav paparazzi
45 12
2,876 2,159
2.4% 2.4%
9.9 9.5
about 14 hours ago 4 days ago
C Kotlin
GNU General Public License v3.0 only Apache License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

inav

Posts with mentions or reviews of inav. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-03-24.

paparazzi

Posts with mentions or reviews of paparazzi. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-03-26.
  • paparazzi 1.3.0 released
    1 project | /r/androiddev | 31 May 2023
  • Building Reddit’s design system for Android with Jetpack Compose
    1 project | /r/RedditEng | 22 May 2023
    Component API tests are written for all components in the library. These are Paparazzi snapshot tests that are parameterized to cover all the combinations of values for the properties in the API of a given component. Additionally, they include as parameters: color theme, layout direction, and optionally other properties that may be relevant to the component under test (e.g., font scale).
  • Compose & Paparazzi: Automatically find @Preview composables at runtime
    2 projects | /r/androiddev | 26 Mar 2023
    Looks really nice. Sadly, I wasn't able to test it because it doesn't support application module
  • Paparazzi 1.2 is out
    3 projects | /r/androiddev | 18 Jan 2023
  • How do you guys test the UI of your app?
    1 project | /r/androiddev | 7 Jan 2023
    Curious what you mean by hilt refuses to work and what you have tried? Usually though if I'm testing the UI of the app, I might use paparazzi for screenshot tests because it doesn't have to run the test on device. Then for a UI integration test for navigation and user flows, use espresso and replace the network data sources with mocks which in your case would be with hilt android test rule and test install in annotation .
  • Improving snapshot tests with Paparazzi
    3 projects | dev.to | 31 Jul 2022
    /** * Finds all files in the components module which have Compose previews * and generates Paparazzi screenshot tests for them. * * The generated tests can then be used to record screenshots with * ./gradlew components:recordPaparazziInternalDebug * * To verify that the current implementation matches the recorded screenshots * ./gradlew components:verifyPaparazziInternalDebug */ fun main() { val path = System.getProperty("user.dir") ?: error("Can't get user dir") // Paparazzi does not currently work in the app module: https://github.com/cashapp/paparazzi/issues/107 // For now this is hardcoded to only check files in the components module. // If we pull our compose files out of the app module to a separate module this code has to be updated. File(path).walk().filter { it.path.contains("/components/src/main/java") && it.extension == "kt" }.forEach { if (it.readText().contains("@Preview")) { processFileWithPreviews(it) } } } /** * Reads the given file, finds the names of all the functions annotated with @Preview * and uses them to generate a Paparazzi test file with one test for each preview. */ private fun processFileWithPreviews(file: File) { val lines = file.readLines() val previewNames = mutableListOf() var saveNextFunctionName = false var packageName = "" lines.forEachIndexed { i, line -> if (i == 0) { packageName = line.split(" ").last() } if (line.contains("@Preview")) { saveNextFunctionName = true } if (saveNextFunctionName && line.startsWith("fun ")) { previewNames += line.split(" ")[1].removeSuffix("()") saveNextFunctionName = false } } val pathString = file.path.replace("src/main", "src/test").split("java").first() + "java" val testFilePath = pathString.toPath() generatePaparazziTest(packageName, file.nameWithoutExtension + "PaparazziTest", testFilePath, previewNames) } fun generatePaparazziTest(packageName: String, fileName: String, path: Path, previewNames: List) { val classBuilder = TypeSpec.classBuilder(fileName) .superclass(PaparazziTest::class) .addAnnotation( AnnotationSpec.builder(Suppress::class) // KotlinPoet does not let us remove redundant public modifiers or Unit return types for the functions, // but we don't mind for generated code as long as the tests work .addMember("\"RedundantVisibilityModifier\", \"RedundantUnitReturnType\"") .build() ) previewNames.forEach { classBuilder.addFunction( FunSpec.builder(it.removeSuffix("Preview").usLocaleDecapitalize()) .addStatement("paparazziRule.snapshot { $it() }") .addAnnotation(Test::class) .build() ) } val testFile = FileSpec.builder(packageName, fileName) .addType(classBuilder.build()) .addFileComment("AUTO-GENERATED FILE by generate_paparazzi_tests.kt\nDO NOT MODIFY") .build() val nioPath = path.toNioPath() testFile.writeTo(nioPath) }
  • Do you do test-based capture & publish for QA? (Espresso, JUnit,..)
    3 projects | /r/androiddev | 9 Jul 2022
  • Paparazzi 1.0 is out
    1 project | /r/androiddev | 3 Jun 2022
  • Mockito and non-debuggable testBuildTypes
    2 projects | /r/androiddev | 2 Jun 2022
    The good thing is, Square got us covered once more, in regards to the flaky emulators, by providing a screenshot-testing library that does not require an emulator: https://cashapp.github.io/paparazzi/
  • Most Efficient Way of Testing Layouts on Various Aspect Ratios/Pixel Densities/Viewport/Resolutions
    1 project | /r/androiddev | 18 May 2022

What are some alternatives?

When comparing inav and paparazzi you can also consider the following projects:

ardupilot - ArduPlane, ArduCopter, ArduRover, ArduSub source

PX4-Autopilot - PX4 Autopilot Software

betaflight - Open Source Flight Controller Firmware

Shot - Screenshot testing library for Android

ExpressLRS-Hardware - STM32/ESP32/ESP8285-based High-Performance Radio Link for RC applications

Mockito - Most popular Mocking framework for unit tests written in Java

cleanflight - Clean-code version of the baseflight flight controller firmware

dropshots - Easy on-device screenshot testing for Android.

EmuFlight - EmuFlight is flight controller software (firmware) used to fly multi-rotor craft.

ESP32 - DroneBridge for ESP32. A transparent short range wifi based telemetry (serial to WiFi) link. Support for MAVLink, MSP, LTM (iNAV) or any other protocol