Running unit test cases in ASP.NET core and angular js application.

Question

0.00/5 (No votes)

See more:

HI,

how to run unit test cases from asp.net core and angular application.

here my project have two solutions asp.net solution and angular solution. asp.net solution is for creating web API's and angular solution is for calling that web API's and doing the CRUD operations.
here problem is if i wants to run angular solution i need to keep a asp.net core solution is in running mode. then only that api's will be in enable mode and we can access data.

here i am doing unit testing in asp.net core solution itself if i keep that solution in running mode "run tests" option will not be visible. if i stop the application from running mode it will be enable so i am not getting any contact with database .

how can i do the unit testing.,
for example i wants to insert some record into database through that unit test case .

Please help me out of this issue.

Thanks in advance.

What I have tried:

I tried with hosting an entire application in IIS so that the application is always visible. that is also not working.

Posted 7-Sep-17 0:45am

Lokesh Rajana

Updated 7-Sep-17 21:12pm

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Eduard Keilholz · Answer 1 · 2017-09-07T21:12:00

Our development environment is in the same situation. We're developing a solution containing web api's (micro services) which have an Angular front-end. For testing, we unit test the API's using SpecFlow and nUnit. We write scenarios which we test by actually starting the API's and posting models (DTO's) back and forth between the API's and test if the outcome is as expected.

On top of the, we use the exact same SpecFlow scenarios to start selenium tests for the front-end. We don't include all tests in these test, but the most important scenarios will be included in these tests as well. This way we make sure that out front-end is still capable of performing the most important tasks for the end-user in each and every version delivered by the team. Front-end tests are pretty expensive to develop / maintain, which is why we don't include all unit test scenarios in the front-end tests as well.

[edit]
This comes close to the solution we use right now for API testing :
End to End Testing of Web API 2 using OWIN and Specflow | Mohammad Ruhul Amin[^]
[/edit]