Project
Reverse Dependencies for platform_helpers
The projects listed here declare platform_helpers as a runtime or development dependency
0.0
Capture STDOUT given a start/stop interface
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
Activity
0.0
Containerize Me is intended to provide a cross distro linux means for easily defining charactieristics of a chroot jail in yaml format. While there are other Linux tools out there aiming at delivering similar solutions often times they differ between distros. With containerize_me it's easy to get hosting setup in chroot jail's in a matter of minutes from any Linux distro.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
Activity
0.0
Validate http request content length vs actual for
elements such as img, link, etc..
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
Activity
0.0
Utility for applying patches to installed gems.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
Activity
0.0
Process Control is a wrapper to allow easy control for any external daemon type process. The
Process Control app is minimal, such that there should never be any errors and the process can
run in a daemon state yielding a consistant means for controlling a child process. The child
process being controlled is done so via signals, QUIT, CONT, HUP, USR1 and TERM (see SIGNALS
section).
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
Activity
0.0
High level calls for searching for process ids and killing processes given a string.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
Activity
0.0
QA Robusta is an automation framework easing pain points away from automation test case writers. How is pain relieved?
* Elements, such as links, buttons, and other html objects are defined in one
location. This ensures over time the user won't have definitions spread out
throughout different layers of code requiring time consuming updates if the
application under test is modified.
* Well defined flows allows the user to have a common means for navigating and
controlling interactions with the application under test. This takes all logic
out of test classes and yields in higher more modular code re-use.
* When an application requiring testing has the elements and flows implemented
less code savy resources can easily add new test cases once trained on how to
access the flows and elements.
* When ever a link or button is clicked a screen shot is taken
* Results are available under site/results directory in html format. Report
includes the rdoc on a per test class method along with any screen shots taken.
Example report: https://cyberconnect.biz/opensource/demo_results.html
* Transparent remote Unix command execution leading to well defined interfaces
for common task. For example, one may have a class defined specifically for
RemoteUnixNetwork. This class would have methods such as, assign_ip, ifup, ifdown,
etc. This class then would be able to perform these task on any remote Unix machine.
* Executes the same on Windows or Linux/Unix environments. Developers have the
freedom to develop on the platform of choice.
* Mechanize extension: Allows the user to define a web application's page elements in
a YAML format and provide navigation paths accessing the YAML structure to interact
with the web application. Users can also perform direct http.post or any other
mechanize functionality when defining state-full interfaces to hit a web application
without going through a browser.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
Activity
0.0
Remote require capabilities.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
Activity