nonnative | Allows you to keep using the power of ruby to test | Unit Testing library

by alexfalkowski Ruby Version: v1.69.1 License: Unlicense

X-Ray Key Features Code Snippets(3)Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | nonnative Summary

nonnative is a Ruby library typically used in Testing, Unit Testing, Docker applications. nonnative has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

Do you love building microservices using different languages?. Do you love testing applications using cucumber with ruby?. Well so do I. The issue is that most languages the cucumber implementation is not always complete or you have to write a lot of code to get it working. So why not test the way you want and build the microservice how you want. These kind of tests will make sure your application is tested properly by going end-to-end. The way it works is it spawns processes or servers you configure and waits for it to start. Then you communicate with your microservice however you like (TCP, HTTP, gRPC, etc).

Support

Quality

Security

License

Reuse

Support

nonnative has a low active ecosystem.

It has 8 star(s) with 1 fork(s). There are 1 watchers for this library.

It had no major release in the last 6 months.

There are 0 open issues and 1 have been closed. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of nonnative is v1.69.1

Quality

nonnative has no bugs reported.

Security

nonnative has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

nonnative is licensed under the Unlicense License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

nonnative releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi has reviewed nonnative and discovered the below as its top functions. This is intended to give you an instant insight into nonnative implemented functionality, and help decide if they suit your requirements.

Adds a process to the specified process .
Processes all ports of the given port
Retrieves command line flags
Adds a hash to the servers .
Connect to the server
Accepts a local socket if it exists
Stop the proxy
Add services to file
Writes data to socket
Sets a run command .

Get all kandi verified functions for this library.

nonnative Key Features

No Key Features are available at this moment for nonnative.

nonnative Examples and Code Snippets

Servers

Ruby

Lines of Code : 147

License : Permissive (Unlicense)

Copy

module Nonnative
  class EchoServer < Nonnative::Server
    def perform_start
      @socket_server = TCPServer.new('0.0.0.0', port)

      loop do
        client_socket = @socket_server.accept
        client_socket.puts 'Hello World!'
        clie

Services

Ruby

Lines of Code : 128

License : Permissive (Unlicense)

Copy

require 'nonnative'

Nonnative.configure do |config|
  config.strategy = :startup

  config.service do |s|
    s.name = 'postgres'
    p.port = 5432
  end

  config.service do |s|
    s.name = 'redis'
    s.port = 6379
  end
end

version: 1.0
strateg

Processes

Ruby

Lines of Code : 49

License : Permissive (Unlicense)

Copy

require 'nonnative'

Nonnative.configure do |config|
  config.strategy = :startup

  config.process do |p|
    p.name = 'start_1'
    p.command = 'features/support/bin/start 12_321'
    p.timeout = config.strategy.timeout
    p.port = 12_321
    p.lo

Community Discussions

Trending Discussions on nonnative

How to add AppleScript/JXA support to non cocoa app?

QUESTION

How to add AppleScript/JXA support to non cocoa app?

Asked 2018-Oct-01 at 12:32

I'm looking into things I can contribute to open source. One pain point I have with many FOSS apps I use is they don't support scripting. I'm thinking it would be nice to at least try to add some basic scripting support to some of the apps I use, e.g. OBS.

However, all the guides for adding scripting support assume that the app in question is written in Cocoa. A lot of these FOSS apps I'm looking at are… not. Does anybody have some good resources for exposing nonnative functionality to native system services, as would be required for scripting?

...

ANSWER

Answered 2018-Oct-01 at 12:32

Implementing non-trivial Apple event support is a right PITA; massively so if you have to implement it from scratch in C/C++ (CocoaScripting.framework is a non-starter for non-Cocoa apps and any third-party frameworks will be massively out of date). Right now I wouldn't even try: AppleScript is dying and JXA is already dead, and Apple are silent on its plans (if any) for the future of Mac Automation. This may change if/when Shortcuts comes to macOS, but that won't happen before 10.15.

If you just want to add really basic automation support (i.e. no 'object model', just simple commands like play FILE/convert FILE) and the app plays nicely with the macOS event loop, it's not hugely difficult (though still extremely tedious) to install Apple event handlers and unpack and pack simple arguments and results (numbers, strings) via the old C Apple Event Manager API. It won't be very "AppleScript-ish", but at least it's achievable. Or, if the app already has its own built-in (e.g. JavaScript) scripting support, implementing a do script CODE [with parameters {ARG1,ARG2,…}] handler to call into that is an easy win.

As far as documentation and example code goes, search for AEInstallEventHandler and see what comes up. Won't be great, but that's as good as it gets. Be prepared to figure out a lot of this stuff for yourself.

Source https://stackoverflow.com/questions/52582482

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install nonnative

Add this line to your application's Gemfile:.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: