NaughtyKeyboard alternatives and similar libraries
Based on the "Other Testing" category.
Alternatively, view NaughtyKeyboard alternatives based on common mentions on social networks and blogs.
PonyDebugger9.5 0.0 L2 NaughtyKeyboard VS PonyDebuggerRemote network and data debugging for your native iOS app using Chrome Developer Tools
iOS Snapshot Test CaseSnapshot view unit tests for iOS
SnapshotTesting📸 Delightful Swift snapshot testing.
ios-snapshot-test-case8.7 0.0 L4 NaughtyKeyboard VS ios-snapshot-test-caseSnapshot view unit tests for iOS
Fakery8.0 1.3 L5 NaughtyKeyboard VS Fakery:alien: Swift fake data generator
Cuckoo7.9 5.8 L3 NaughtyKeyboard VS CuckooBoilerplate-free mocking framework for Swift!
Mockingjay7.8 0.0 L4 NaughtyKeyboard VS MockingjayAn elegant library for stubbing HTTP requests with ease in Swift
OCMockito7.1 2.1 NaughtyKeyboard VS OCMockitoMockito for Objective-C: creation, verification and stubbing of mock objects
Buildasaur6.5 0.0 L3 NaughtyKeyboard VS BuildasaurAutomatic testing of your Pull Requests on GitHub and BitBucket using Xcode Server. Keep your team productive and safe. Get up and running in minutes. @buildasaur
DVR6.4 0.0 L5 NaughtyKeyboard VS DVRNetwork testing for Swift
Kakapo6.2 0.0 L3 NaughtyKeyboard VS Kakapo🐤Dynamically Mock server behaviors and responses in Swift
trainer4.2 0.0 L5 NaughtyKeyboard VS trainerConvert xcodebuild plist and xcresult files to JUnit reports
Vinyl4.2 0.0 L4 NaughtyKeyboard VS VinylNetwork testing à la VCR in Swift
Cribble3.9 0.0 L5 NaughtyKeyboard VS CribbleSwifty tool for visual testing iPhone and iPad apps. Every pixel counts.
Mockingbird3.5 0.0 NaughtyKeyboard VS MockingbirdSimplify software testing, by easily mocking any system using HTTP/HTTPS, allowing a team to test and develop against a service that is not complete or is unstable or just to reproduce planned/edge cases.
MirrorDiffKit3.1 0.0 L2 NaughtyKeyboard VS MirrorDiffKitGraduation from messy XCTAssertEqual messages.
Mockit3.1 0.0 L4 NaughtyKeyboard VS MockitA simple mocking framework for Swift, inspired by the famous http://mockito.org/
second_curtainUpload failing iOS snapshot tests cases to S3
AcceptanceMark1.9 0.0 L4 NaughtyKeyboard VS AcceptanceMarkTool for generating Acceptance Tests in Xcode, inspired by Fitnesse
MetovaTestKit1.6 0.0 L4 NaughtyKeyboard VS MetovaTestKitA collection of useful test helpers designed to ease the burden of writing tests for iOS applications.
SnappyTestCaseiOS Simulator type agnostic snapshot testing, built on top of the FBSnapshotTestCase.
XCTestExtensionsXCTestExtensions is a Swift extension that provides convenient assertions for writing Unit Test.
TestKit0.6 0.0 L3 NaughtyKeyboard VS TestKitThe easiest way to implement full BDD in your Swift iOS projects! Use plain English specs (Gherkin) to drive tests that include both UI automation and interacting with application data & state.
Bugfender LiveStream the screen of an iOS device for live debugging.
Fetcher0.3 2.6 NaughtyKeyboard VS FetcherMock paging data with a variable fetch time interval.
DataFixture0.3 0.0 NaughtyKeyboard VS DataFixtureCreation of data model easily, with no headache.
Parallel iOS TestsRun iOS tests on multiple simulators in parallel at the same time
OCMockMock objects for Objective-C.
Appwrite - The Open Source Firebase alternative introduces iOS support
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of NaughtyKeyboard or a related project?
The Big List of Naughty Strings is a list of strings which have a high probability of causing issues when used as user-input data.
I have put together these strings to create Naughty Keyboard – a very simple iOS app that gives you access to a custom keyboard to use these strings to test your application.
Clone the app, run it from Xcode then activate the keyboard. I'm pretty sure Apple wouldn't allow me to put this on the App Store.
This project comes with a syncing mechanism to be able to be up-to-date with the latest strings from the Big List of Naughty Strings.
The way this project is structured is by using
App Groups and sharing the
UserDefaults instance across the extension and the main app as well as the synced file with the naughty strings.
In order to do this there's a couple of things that need to be done before compiling and running the project:
- Set the project’s bundle identifier prefix.
- Select your development team.
- Create provisioning profiles.
1. Set the Project’s Bundle Identifier Prefix
NaughtyStrings project -> Build Settings and change the
User Defined value
NAUGHTYSTRINGS_BUNDLE_PREFIX to a globally unique reverse DNS string for your own
2. Select Your Development Team
Select your paid iOS Developer Program account as the development team for each of the four targets below:
3. Create Provisioning Profiles
Create a provisioning profile for each of the three targets below:
Xcode helps you to create these provisioning profiles. First, select the
NaughtyStrings project in
Xcode's project navigator. Then, for each of the three targets listed above:
- Select the target in the Targets list.
- Select the General tab in the right-hand pane.
- In the Identity section, under the Team popup menu, click Fix Issue.
- Xcode will download a new provisioning profile for that target. (This process may take up to 30 seconds per target.)
The Big List of Naughty Strings (and this keyboard) is intended to be used for software you own and manage. Some of the Naughty Strings can indicate security vulnerabilies, and as a result using such strings with third-party software may be a crime. The maintainer is not responsible for any negative actions that result from the use of the list.
- Romain Pouclet (palleas)
NaughtyKeyboard may be freely distributed under the MIT License. See the
The application icon is based on icons Tyler Glaude and Herbert Spencer from The Noun Project. Used under a Creative Commons BY 3.0 license.
*Note that all licence references and agreements mentioned in the NaughtyKeyboard README section above are relevant to that project's source code only.