Programación by JMR

eHow (Computacion)

JMR — 2014-04-29 16:28:02 UTC

eHow (VBA)

JMR — 2014-04-29 16:28:17 UTC

White-box testing

JMR — 2014-04-29 19:47:34 UTC

White-box testing (also known as clear box testing, glass box testing, transparent box testing, and structural testing) is a method of testing software that tests internal structures or workings of an application, as opposed to its functionality (i.e. black-box testing). In white-box testing an internal perspective of the system, as well as programming skills, are used to design test cases. The tester chooses inputs to exercise paths through the code and determine the appropriate outputs. This is analogous to testing nodes in a circuit, e.g. in-circuit testing (ICT).

While white-box testing can be applied at the unit, integration and system levels of the software testing

Levels

Unit testing.

White-box testing is done during unit testing to ensure that the code is working as intended, before any integration happens with previously tested code. White-box testing during unit testing catches any defects early on and aids in any defects that happen later on after the code is integrated with the rest of the application and therefore prevents any type of errors later on.

2. Integration testing.

White-box testing at this level are written to test the interactions of each interface with each other. The Unit level testing made sure that each code was tested and working accordingly in an isolated environment and integration examines the correctness of the behaviour in an open environment through the use of white-box testing for any interactions of interfaces that are known to the programmer.

3. Regression testing.

White-box testing during regression testing is the use of recycled white-box test cases at the unit and integration testing levels.

White-box test design techniques include:

Control flow testing
Data flow testing
Branch testing
Path testing
Statement coverage
Decision coverage

http://en.wikipedia.org/wiki/White-box_testing

Blackbox debugging

JMR — 2014-04-29 20:33:25 UTC

Blackbox debugging involves the separation of a program's parts in order to diagnose where an error lies. To "blackbox" the program is to divide the parts involved in execution, test them separately as much as possible, and determine which parts are working and which are failing. Blackbox debugging is frequently used in computer programming for troubleshooting bugs or other unexpected behaviour.

http://python.about.com/od/programmingglossary/g/defblackbox.htm

Udemy Unity 3d

JMR — 2014-05-01 10:44:58 UTC

https://www.udemy.com/unity-3d-game-development-ios-android-web-beginners

Unity

JMR — 2014-05-01 10:45:42 UTC

Unity Forums

JMR — 2014-05-01 10:50:42 UTC

Unity Answers

JMR — 2014-05-01 10:51:00 UTC

UnityManual (local file)

JMR — 2014-05-01 10:51:47 UTC

file:///C:/Program Files (x86)/Unity/Editor/Data/Documentation/Documentation/Manual/UnityBasics.html

Unity Tutorials

JMR — 2014-05-01 10:52:49 UTC

Rebel (Tech)

JMR — 2014-05-01 11:16:40 UTC

https://www.rebelmouse.com/JoseMariaRocaGonzalez/Tech/

PUBLIC

JMR — 2014-05-01 11:53:40 UTC

Tutorials Youtube Unity

JMR — 2014-05-04 12:21:42 UTC

Merge this

JMR — 2014-05-04 12:22:04 UTC

http://es.padlet.com/JMR/CodingJMR

LUA online manual

JMR — 2014-05-05 17:33:19 UTC

Guía compilación entorno en c++

http://lua-users.org/wiki/BuildingLuaInWindowsForNewbies

LUA comment

JMR — 2014-05-05 17:40:19 UTC

As others mentioned Lua is "do it yourself" kind of environment. Also it is very fast and quite memory efficient compared to Perl/PHP/Python/Ruby especially if you are using LuaJIT. And it is very easy to integrate with C/C++ code. Usually these points are irrelevant for a typical web application where performance is usually restricted by database. Also where you don't really care about C/C++ integration and where you don't really want to do things yourself but rather you want to build on top of existing frameworks. For this reason I don't think Lua is a good fit for a typical web applications.

LUA vs Python

JMR — 2014-05-05 17:48:03 UTC

http://lua-users.org/wiki/LuaVersusPython