Testing/es: Difference between revisions

From FreeCAD Documentation
(Updating to match new version of source page)
(Updating to match new version of source page)
 
(36 intermediate revisions by 4 users not shown)
Line 1: Line 1:
<languages/>
<languages/>

{{docnav
{{Docnav/es
|[[Debugging|Debugging]]
|[[Debugging/es|Depuración]]
|[[Continuous Integration|Continuous Integration]]
|[[FreeCAD_Build_Tool/es|FreeCAD Herramienta Compilación]]
}}
}}


[[Image:Workbench_Test.svg|64px]]
[[Image:Workbench_Test.svg|thumb|128px|Icono del ambiente Prueba]]

<div class="mw-translate-fuzzy">
== Introducción ==
Esta es la lista de aplicaciones de prueba a partir de 0.15 Git 4207:
</div>


{{TOCright}}
{{TOCright}}

== Introducción ==


<div class="mw-translate-fuzzy">
<div class="mw-translate-fuzzy">
El [[Testing/es|Ambiente de trabajo del marco Pruebas]] no es realmente un ambiente de trabajo de modelado, pero contiene un conjunto de scripts de [[Python/es|Python]] para realizar diferentes pruebas en los componentes principales de FreeCAD, con el fin de depurar problemas. Ver también [[debugging/es|depuración]].
FreeCAD incorpora un extenso entorno de pruebas. Las pruebas se basan en un conjunto de archivos de guión de Python ubicados en el módulo test.
</div>
</div>


You can run the tests from the command line, by using the {{incode|-t}} or {{incode|--run-test}} options.
Puede ejecutar las pruebas desde la línea de comandos, utilizando las opciones {{incode|-t}} o {{incode|--run-test}}.


Ejecutar todas las pruebas:
Run all tests:


{{Code|code=
{{Code|code=
Line 26: Line 24:
}}
}}


Ejecutar sólo algunas de las pruebas unitarias especificadas, por ejemplo:
Run only some the specified unit test, for example:


{{Code|code=
{{Code|code=
Line 32: Line 30:
}}
}}


If a test does not need the GUI, it can also be executed in console mode by setting the {{incode|-c}} or {{incode|--console}} option in addition. This usually results in much faster startup time as the GUI is not loaded. For example:
== Test menu ==


{{Code|code=
Each top level directory in FreeCAD should have a file with the tests that can be run for that particular workbench or module. The file usually starts with the word {{incode|Test}}.
freecad -c -t TestPartDesignApp
}}


== Menú de prueba ==
To run a test from within FreeCAD, switch to the Test Workbench, then {{MenuCommand|Test commands → TestToolsGui → Self test → Select test name}}, then enter the name of the Python file with the tests; for example, for the [[Draft Workbench|Draft Workbench]], this would be {{MenuCommand|TestDraft}}, then press {{Button|Start}}.


Cada directorio de nivel superior en FreeCAD debe tener un archivo con las pruebas que se pueden ejecutar para ese ambiente de trabajo o módulo en particular. El archivo suele empezar con la palabra {{incode|Test}}.
== Test functions ==

This is the list of test apps as of 0.15 git 4207:
Para ejecutar una prueba desde FreeCAD, cambia al ambiente de trabajo Pruebas, luego {{MenuCommand|Comandos de prueba → TestHierramientasGui → Autoprueba → Seleccionar nombre de la prueba}}, luego introduce el nombre del archivo Python con las pruebas; por ejemplo, para el [[Draft Workbench/es|Ambiente de trabajo Borrador]], esto sería {{MenuCommand|PruebaBorrador}}, luego presiona {{Button|Inicio}}.

== Funciones de prueba ==

Esta es la lista de aplicaciones de prueba a partir de la versión 0.15 git 4207:


=== TestAPP.All ===
=== TestAPP.All ===

Add test function
Add test function


=== BaseTests ===
=== BaseTests ===

Add test function
Add test function


=== UnitTests ===
=== UnitTests ===

Add test function
Add test function


=== Document ===
=== Documento ===

Add test function
Add test function


=== UnicodeTests ===
=== UnicodeTests ===

Add test function
Add test function


=== MeshTestsApp ===
=== MeshTestsApp ===

Add test function
Add test function


=== TestDraft ===
=== TestDraft ===

Add test function
Add test function


=== TestSketcherApp ===
=== TestSketcherApp ===

Add test function
Add test function


=== TestPartApp ===
=== TestPartApp ===

Add test function
Add test function


=== TestPartDesignApp ===
=== TestPartDesignApp ===

Add test function
Add test function


=== Workbench ===
=== TestPathApp ===

Path workbench test cases:
* depthTestCases:
* PathTestUtils:
* TestDressupDogbone: Test functionality of Dogbone dressup.
* TestHoldingTags: Test functionality of Holding Tags dressup.
* TestPathAdaptive: Test selection capability of Adaptive operation.
* TestPathCore: Test core functionality of Path workbench.
* TestPathDeburr: Test general functionality of Deburr operation.
* TestPathGeom: Test various functions available in the PathGeom module.
* TestPathHelix: Test general functionality of Helix operation.
* TestPathLog: Test various functions available in the PathLog debugging and feedback module.
* TestPathOpTools:
* TestPathPreferences: Test various functions available in the PathPreferences module.
* TestPathPropertyBag:
* TestPathSetupSheet:
* TestPathStock:
* TestPathThreadMilling:
* TestPathTool:
* TestPathToolBit:
* TestPathToolController:
* TestPathTooltable:
* TestPathUtil: Test various functions available in the PathUtil module.
* TestPathVcarve: Test general functionality of Vcarve operation.
* TestPathVoronoi:

=== Ambiente de trabajo ===

Add test function
Add test function


=== Menu ===
=== Menú ===

Add test function
Add test function


=== Menu.MenuDeleteCases ===
=== Menu.MenuDeleteCases ===

Add test function
Add test function


=== Menu.MenuCreateCases ===
=== Menu.MenuCreateCases ===

Add test function
Add test function


==Guionización==
<div class="mw-translate-fuzzy">
{{docnav|Debugging|Continuous Integration}}
</div>


{{Emphasis|Ver también:}} [[FreeCAD_Scripting_Basics/es|Básicos de Guionización FreeCAD]].
{{Userdocnavi}}


===Get a list of all top-level test modules===
[[Category:Developer Documentation]]


{{Code|code=
[[Category:Test Framework]]
FreeCAD.__unit_test__
}}

Note that the test modules returned here depend on whether a GUI available or not. I.e. when executed in console mode, various tests ending in "Gui" are missing.

===Run specific tests===

There are various ways of running tests using [https://docs.python.org/3/library/unittest.html Python's unittest library]. FreeCAD's test framework removes some of the boiler plate for the most common cases.

Run all tests defined in a Python module:
{{Code|code=
import Test, TestFemApp
Test.runTestsFromModule(TestFemApp)
}}

Run all tests defined in a Python class:
{{Code|code=
import Test, femtest.app.test_solver_calculix
Test.runTestsFromClass(femtest.app.test_solver_calculix.TestSolverCalculix)
}}

===Ejemplo 1===

Within the Python Console of FreeCAD, the following code format may be used to run built-in tests. Replace the red "'''TestFem'''" text in the code below with the desired module test name.
* For example, use "'''TestPathApp'''" to run all unit tests for the Path workbench unit test framework.
* Submodules are available using dot notation, like "'''TestPathApp.TestPathAdaptive'''" to only run the Adaptive unit tests within the greater Path workbench test framework.
* Multiple test modules or submodules may be combined by adding another `'''suite.addTest(...)'''` method call just like the one in the code below, but with a different module or submodule reference.
* Output for the code below will be in the Report View panel within the FreeCAD GUI.
* Code source is copied from post by FreeCAD forum user, ''sgrogan'', in the [https://forum.freecadweb.org/viewtopic.php?style=3&p=153251#p153251 unit tests per python] topic, with credit there given to forum user, ''wmayer''.

{{Code|code=
import unittest
suite = unittest.TestSuite()
suite.addTest(unittest.defaultTestLoader.loadTestsFromName("TestFem"))
r = unittest.TextTestRunner()
r.run(suite)
}}

==Recursos adicionales==

===Temas del foro===

* [https://forum.freecadweb.org/viewtopic.php?style=3&f=27&t=18379 Support for running specific unit tests with --run-test #331]


{{Docnav/es
|[[Debugging/es|Depuración]]
|[[FreeCAD_Build_Tool/es|FreeCAD Herramienta Compilación]]
}}


<!--T:21-->
[[Category:Workbenches]]
{{Userdocnavi{{#translation:}}}}
[[Category:Testing]]
[[Category:Developer Documentation{{#translation:}}]]
[[Category:Test Framework{{#translation:}}]]
[[Category:Workbenches{{#translation:}}]]
[[Category:Testing{{#translation:}}]]

Latest revision as of 09:30, 28 January 2022

Icono del ambiente Prueba

Introducción

El Ambiente de trabajo del marco Pruebas no es realmente un ambiente de trabajo de modelado, pero contiene un conjunto de scripts de Python para realizar diferentes pruebas en los componentes principales de FreeCAD, con el fin de depurar problemas. Ver también depuración.

Puede ejecutar las pruebas desde la línea de comandos, utilizando las opciones -t o --run-test.

Ejecutar todas las pruebas:

freecad --run-test 0

Ejecutar sólo algunas de las pruebas unitarias especificadas, por ejemplo:

freecad -t TestDraft

If a test does not need the GUI, it can also be executed in console mode by setting the -c or --console option in addition. This usually results in much faster startup time as the GUI is not loaded. For example:

freecad -c -t TestPartDesignApp

Menú de prueba

Cada directorio de nivel superior en FreeCAD debe tener un archivo con las pruebas que se pueden ejecutar para ese ambiente de trabajo o módulo en particular. El archivo suele empezar con la palabra Test.

Para ejecutar una prueba desde FreeCAD, cambia al ambiente de trabajo Pruebas, luego Comandos de prueba → TestHierramientasGui → Autoprueba → Seleccionar nombre de la prueba, luego introduce el nombre del archivo Python con las pruebas; por ejemplo, para el Ambiente de trabajo Borrador, esto sería PruebaBorrador, luego presiona Inicio.

Funciones de prueba

Esta es la lista de aplicaciones de prueba a partir de la versión 0.15 git 4207:

TestAPP.All

Add test function

BaseTests

Add test function

UnitTests

Add test function

Documento

Add test function

UnicodeTests

Add test function

MeshTestsApp

Add test function

TestDraft

Add test function

TestSketcherApp

Add test function

TestPartApp

Add test function

TestPartDesignApp

Add test function

TestPathApp

Path workbench test cases:

  • depthTestCases:
  • PathTestUtils:
  • TestDressupDogbone: Test functionality of Dogbone dressup.
  • TestHoldingTags: Test functionality of Holding Tags dressup.
  • TestPathAdaptive: Test selection capability of Adaptive operation.
  • TestPathCore: Test core functionality of Path workbench.
  • TestPathDeburr: Test general functionality of Deburr operation.
  • TestPathGeom: Test various functions available in the PathGeom module.
  • TestPathHelix: Test general functionality of Helix operation.
  • TestPathLog: Test various functions available in the PathLog debugging and feedback module.
  • TestPathOpTools:
  • TestPathPreferences: Test various functions available in the PathPreferences module.
  • TestPathPropertyBag:
  • TestPathSetupSheet:
  • TestPathStock:
  • TestPathThreadMilling:
  • TestPathTool:
  • TestPathToolBit:
  • TestPathToolController:
  • TestPathTooltable:
  • TestPathUtil: Test various functions available in the PathUtil module.
  • TestPathVcarve: Test general functionality of Vcarve operation.
  • TestPathVoronoi:

Ambiente de trabajo

Add test function

Menú

Add test function

Menu.MenuDeleteCases

Add test function

Menu.MenuCreateCases

Add test function

Guionización

Ver también: Básicos de Guionización FreeCAD.

Get a list of all top-level test modules

FreeCAD.__unit_test__

Note that the test modules returned here depend on whether a GUI available or not. I.e. when executed in console mode, various tests ending in "Gui" are missing.

Run specific tests

There are various ways of running tests using Python's unittest library. FreeCAD's test framework removes some of the boiler plate for the most common cases.

Run all tests defined in a Python module:

import Test, TestFemApp
Test.runTestsFromModule(TestFemApp)

Run all tests defined in a Python class:

import Test, femtest.app.test_solver_calculix
Test.runTestsFromClass(femtest.app.test_solver_calculix.TestSolverCalculix)

Ejemplo 1

Within the Python Console of FreeCAD, the following code format may be used to run built-in tests. Replace the red "TestFem" text in the code below with the desired module test name.

  • For example, use "TestPathApp" to run all unit tests for the Path workbench unit test framework.
  • Submodules are available using dot notation, like "TestPathApp.TestPathAdaptive" to only run the Adaptive unit tests within the greater Path workbench test framework.
  • Multiple test modules or submodules may be combined by adding another `suite.addTest(...)` method call just like the one in the code below, but with a different module or submodule reference.
  • Output for the code below will be in the Report View panel within the FreeCAD GUI.
  • Code source is copied from post by FreeCAD forum user, sgrogan, in the unit tests per python topic, with credit there given to forum user, wmayer.
import unittest
suite = unittest.TestSuite()
suite.addTest(unittest.defaultTestLoader.loadTestsFromName("TestFem"))
r = unittest.TextTestRunner()
r.run(suite)

Recursos adicionales

Temas del foro