If you have specifications that say a confirmation must be displayed, the test fails.
If you have user requirements or user expectations that there will be a confirmation dialog, the test fails.
In the situation you describe, I would create a bug from the test, but it would have a lower severity rating because it doesn't interfere with functionality. The ...
For that, you need to create a clone of the test case, for that you may use the following steps
Go the test case and right click on it.
Click on Create Copy and add to suite option in the list.
Make the change if you want (Here you can modify test case independently without affecting other).
Click on Save and Close.
Now drag and drop that test case to ...
If it is an Angular application I would go for Protractor
Protractor was made for Angular Apps. You don't have deal with elements not being visible yet due to page loads. Protractors deals with it for you
As far as I know CodedUI des not provide this functionality. Correct me if I'm wrong.
The Microsoft stack is surprisingly still very popular, regardless of other cheaper alternatives.
TFS is basically the central repository. Call it git and Jenkins rolled into one. It manages version control as well as builds.
MTM is just Microsoft's test management tool. This is very useful for linking a manual test that has been created within MTM (its ...
If you are a programmer you need Microsoft Visual Studio Enterprise which is $5,999/user/first year and includes Team Foundation Server online access & Microsoft Test Manager stand alone app.
Anyone doing just QA and no programming can use Visual Studio Test Professional which will cost your company less $2,169/user/first year and only includes Team ...
Without the Reporting Server, your only option to get this information is through the TFS API. This is because TFS does not directly associate test results with test cases: instead there is an implicit linkage through a test run with test points.
The short version is that each test case may be associated with one or more test runs.
Each test run will have ...
A lot. The last I heard, MTM will be deprecated once the test-specific functionality of the TFS web portal is available.
Create backlog items (in TFS) - the UI is a lot better, and there's been a lot of improvement to backlog item management and iteration management.
Create tasks (in TFS) - see above.
Design test cases (in TFS, VS, or MTM) - the TFS UI is ...
As long as your version of TFS is capable of using the TFS Marketplace (i.e. you have TFS2015 or above, or you are actually using VSTS), then yes, it's possible.
This question gives more information and some useful links.
The TFS Marketplace has numerous plugins - the question I linked above shows how to use the Maven plugin to run TestNG tests.
First up, your boss is going to want to see this information in a convenient form. TFS allows this without much extra work on your part.
You can use TFS (if it's a recent enough version) to set up scheduled runs for your test automation. Reports of your runs then become an automatic thing - and you can arrange for them to be emailed to whoever needs ...
It may depend on the strategy of your project, but i'd say this test is failed. If the confirmation is part of your specifications/functional need, you can't make this test pass.
Imagine this is the only issue in your whole test plan, if you pass the test, then your indicators will be all green for this functionality. Thus, there is no reason to do rework, ...
Have you looked into TestComplete? We use it at my company and have found it to be very versatile and the SmartBear folks are excellent to work with.
AFAIK there are certain limitations to the online version of the tool.
Here is a screenshot of how it looks on my side in Microsoft Test Manager.
There also some information at the bottom that can`t be seen in the SS below reering to Links and History.
You can simply create a new work item type called "Test", and customise it to have the fields you require. You will need to add fields like Result (Not Run, Passed, Failed, In Progress etc), Tested by, Date executed and Tested in Build, etc.
You will need to make these fields reportable in the data warehouse, and build some status reports.
Once you have ...
Check the official documentation. It isn't specific to testers. For that read, Application Lifecycle Management with Visual Studio Team Foundation Server.
At the onset of learning anything new, I usually watch the most viewed video on YouTube for my term as a primer.
You can directly run tests in TFS with Typemock's SmartRunner Task, It integrates with TFS, TeamCity, and more build servers.
It is part of the Isolator bundle, I think it has a free version, you should check it.
In Excel, I do the following
Go to Team Tab and then click on New List,
Connect to your TFS
Choose Input List then click OK
Click on choose columns so we get all the necessary ones for creating test cases.
The Work Item item is set to "All Work Item Types", change this to "Test Case"
Click Add Required and you should have about 8 columns, the click ok
It depends on whether you ship the software.
For company-internal software, a Wiki works fine. MediaWiki is free; Confluence requires a license fee but is popular. Atlassian, the maker of Confluence, also makes Jira, a popular bug tracking tool. Jira requires a license fee too. You can query Jira, stuff the results into a Confluence page, and then edit ...
The Team section on excel will allow you to connect to and export any TFS query you have access to. Queries will work against any TFS object that has a base type of Work Item.
Since a requirements-based test suite uses (in the Scrum template) Product Backlog Items and Defects to define requirements, you need to build a query in TFS that includes linked work ...
There could be a number of other ways but the best I could found is to follow these steps:
Launch MTM and navigate to "Analyze Test Runs".
Select tests based on "View" and "Start date range".
Use Ctrl+c to copy the records.
Open Excel and use Ctrl+v to paste the records.
You should be able to select additional columns by right clicking the header row ...
There are two options to do this.
When you enter a requirement in the “Requirements” module, you can link it to a test through “Test Coverage” sub module, provided a relevant test exists.
When you write a test in the “Test Plan” module, you can link it to a requirement through “Req Coverage” sub module, provided a relevant requirement exists.
Scrum teams should not have dependencies on other teams to release their changes.
So a good practise would be to let the Scrum to run the automation, maybe even integrate someone from your group into their team to make it truly cross functional.
Scrum is about enabling teams to self-organize towards a process that
maximizes their ability to frequently ...
I suspect it depends on where you're creating the test case, and what version you're using.
Microsoft Test Manager 2013 doesn't have a limit - I just created a shared step with 13 steps.
Your version of the TFS web portal may not support this: TFS 2012 web portal doesn't support creating shared steps at all.
VSTS has a limit of 10 steps to create shared ...
Not sure what version of TFS you are currently using, but you can:
Work -> Backlog -> Current sprint -> And in the top header you should have a NEW button.
Creating them via this route will add them to the current sprint board - and you can drag/drop their position as you wish. Or you can link them to a current PBI/User story.
We use MS TFS for tracking bugs and enhancements then we query the repository through the TFS APIs and write the content on MS Word template.
Edit: there are more ways for querying the TFS database, the simplest is creating a new TFS report with your preferred layout and execute it on a regular basis. The report outcome can be exported in several formats, ...
I would recommend a Wiki.
This would allow you and your team to collaboratively update the release notes and also maintain versioning (a very important feature when you look back after something went wrong!)
Couple of free options;
Both can contain links to your other tools but if you want full integration it often comes at a cost like;
As far as I know there are two ways to import work items to TFS.
Mass add/edit using Excel: https://msdn.microsoft.com/en-us/library/dd286627.aspx
Test Case Migrator(Not updated for the newest TFS version): http://tcmimport.codeplex.com/
First you need to create your test cases in MTM and enter values for the parameters in the Parameters section of the test cases (I guess this you have already achieved).
Now, you move to the 'Test' tab of your MTM and select the child tab 'Run Tests', add your test suite to be executed to this tab (if not already added). Then, when you click the 'Run' ...
As far as I know, you an only see the changes in the History section of the Summary Tab, but there is no way to revert the changes made to the test cases. Refer to this post for more details on this