> For the complete documentation index, see [llms.txt](https://abi.gitbook.io/net-core/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://abi.gitbook.io/net-core/10.-pruebas-de-integracion/10.2-configurando-specflow.md).
# 12.3 Configurando Specflow
De momento la extensión de Specflow no esta disponible para Visual Studio for Mac, por lo tanto utilizaré Visual Studio para Windows
Para poder generar las pruebas con specflow se necesita la extensión **Specflow for Visual Studio 2019.**
Para instalar una extensión ve al menú **Extensiones** -> **Administrar extensiones**
Buscamos la extensión **SpecFlow for Visual Studio 2019** y damos clic en el botón **Download**
Damos click en **Modify**
Agregamos los siguientes paquetes nuget.
Primero instalamos el paquete de SpecFlow
```
Install-Package SpecFlow
```
Instalamos el paquete specflow para MSTest, si fuera xUnit, elegimos el de xUnit (Specflow\.xUnit)
```
Install-Package SpecFlow.MsTest
```
Instalamos este paquete el cual nos permite enlazar el código
```
Install-Package SpecFlow.Tools.MsBuild.Generation
```
Puedes ver la documentación oficial aquí
{% embed url="" %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://abi.gitbook.io/net-core/10.-pruebas-de-integracion/10.2-configurando-specflow.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.