![]() In addition, I suggest that you can run your upgraded solution on another machine having VS2012 to check if all tests can show up. Whether do you get any errors when you upgrade to VS2012? If yes, youĬan provide us detailed error information. ![]() Generally if you upgrade a solution to VS2012, all tests can show up after you build solution in VS2012. I would like to know which point all the missing test methods were visible. “at one point all the missing test methods were visible” If you are only working with unit test projects and unit tests, what result will you get? ![]() If you re-start your VS2012, open your solution and build your solution, will you still see the same issue?Īlso I suggest that you create a Coded UI Test solution and some projects in it and create some coded UI tests in each project, then you build the solution to check if the same issue will occur. If they are private methods, they can’t be shown up in Test Explorer. If all your tests are coded UI test in the same solution, I suggest that you can check if those methods that are not showing up in Test Explorer are public. I would like to know if all of them are coded UI test and are in different project within the same solution. If yes, let’s look at the issue step by step. Do you mean that some methods in coded UI test project don’t display in Test Explorer but some methods can show up?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |