Test Manager for Trac questions - testing

I'm looking for a way to better manage a list of test cases within Trac. The Test Manager plugin for Trac seems to be the obvious choice.
Anyone have experience, comments and/or concerns with the Test Manager plugin for Trac?
We've also looked at Testuff, which has an awesome "Test Runner" app that integrates with Trac for creating tickets. However, it stores all of the test cases, labs, etc on their servers. I'd really like to have a single destination for documentation, tickets and tests (i.e. Trac).
We're using SnagIt for screen capture and annotations today. We're looking at the Problem Steps Recorder in Windows. We'd like to find something that can send captures to Trac, similar to the Testuff-Trac integration.
Any suggestions for an app that can capture video/images with each mouse click and key press logged? BONUS: Attach capture(s) into a new Trac ticket.

For capturing movies and uploading into Trac, try http://www.bbtestassistant.com/
For single screen captures, annotation and uploading into Trac, try http://fat-bug.com
I have also written a plugin for Cropper, http://cropper.codeplex.com/, that will let you upload images but it does not support annotations before hand like fat bug. Let me know if you want a copy of that.

We used Test Manager Plugin For Trac in one of my previous projects and I can say that it worked fine for us. It provides bidirectional traceability between Test Cases and user stories, support test plans (which in my point of view are execution plans but incorporated with wiki page become test plan) and it also as most of the Trac plugins allow to be customized in order to satisfy the process needs.

Related

Automating Functional Test

I am a person who works as a SW QA in Korea. I have used Jira Old Version(Local System) to Track issue out and github to manage Site Source. Now i am considering to change Test System. until now, i have had to test all function that was updated in my solution manually!!. so i start wondering how i can automate this. What i want is to test main system and sub system(function) with using program like Postman. So i hope you recommend some programs to test what i want all.
Test Priority is Automation of that below
easy use
Main Source Test
Sub(Function) Source Test
please, i will wait for your answer
I have used Jira Old Version(Local System) to Track issue out and github to manage Site Source. i want to automate all test including black box, UI function.

CRUD with single drag/drop or other action via API?

This is my first post/question. If I missed an existing thread that answers my question, I missed that thread in my search and definitely appreciate you linking me! Please let me know if I should be posting/asking this elsewhere....
My question relates to Salesforce.
I have a use case where a client has a monthly batch of files that need to be made available on various cloud-based storage/distribution platforms like Box and Dropbox but also other less ubiquitous tools specific to the sector. Currently, the client is logging into each distribution platform, one-at-a-time, and uploading the files; then, if at any point any files need to be updated or removed/restricted, the client logs into each platform one-by-one and takes the necessary action. Obviously the process being described is tedious/laborious and leaves multiple gaps for error. The client and I are discussing a solution that would allow for create/read/update/delete actions in all of the distribution platforms without having to leave their Salesforce org. I am aware of existing AppExchange integrations for Box, Dropbox, etc. but they don’t quite do everything we need (to my knowledge)—they tie-in nicely and there are use cases where they are powerful tools...but—my understanding of those existing integration is that they would still each require dedicated tabs within the Object and repeated ‘drags’ and ‘drops’ of the same files to each tab. Again, the end goal here is that, for example, the client wants to drag and drop one time and have it pushed to the various platforms, etc. Or another example is they would like to choose "delete" one time from within Salesforce and have the file removed/restricted on all distribution platforms.
I am a certified SF Admin 1, so...perhaps this should be in my wheelhouse but...I feel unsure how to approach. My feeling is this is asking for a combination of integrations via API and Process/Flow work, but I am hoping for some ideas/input/guidance. Any insight or help any of you have to offer would be so greatly appreciated!!
Thanks so much!

Setting values whitout UI interaction. Cypress app actions

Guys! I'm kinda new in cypress and was looking in this link (https://www.cypress.io/blog/2019/01/03/stop-using-page-objects-and-start-using-app-actions/ )to see the diff between page objects and app actions. Since app actions are brand new, i was not able to find any documentation to help me out. In the link above, there was an example of how to predefine values ​​on the page so no UI interaction is required. I was able to follow the steps and realize the changes here, but i don't know how to do that outside this example.
How could i manipulate cypress application to do that?
Skimming the article, the idea of application actions is to export an API/hooks from your application that your test can use to interact with the app (its model, state etc.), for the purpose of speeding up certain workflows (such as seeding the model), awaiting certain events etc.
There's nothing magical about it, but it requires knowing your app architecture — what you need to export (i.e. expose on the window object), and how to interact with it. If you're not the developer of the app (e.g. you work in a separate QA department), and treat the app as a black box, then you'll need to discuss with the dev team how best to implement this.
Each app is different, and depending on the app architecture (What framework does it use? How does it store state/model? etc.), each solution will be different.

Launching selemium scripts from browser for screen capture

I am looking for creating a functional training package for a web based product (more like a screen capture).
However, the requirement is not just to have screen capture, but to have a test mode for the training where we can prompt the user to click on the screen and check if they have done proper flow.
for e.g. A banker will first go through the screen capture to see "how to open an account" in the core banking application . Later user will be presented with a test where user has to click through all the controls and flow.
I have seen selenium being used for authoring good UI automation test cases, so I wanted to explore the possibility of using selenium for creating these training modules
These training modules needs to be launched from intranet application. Is it possible to launch selenium authored UI automation test cases from the browser? I want to stay away from writing any extensions or plugins.
I haven't used selenium and I might be completely off tangent here, so any other suggestion to achieve this using open source tools are welcome.
Without writing any scripts, you may consider downloading Selenium IDE. It has a recording and replay function that may meet your need.
For a fast tutorial, please follow this link.
https://www.youtube.com/watch?v=gsHyDIyA3dg
Hope it helps.

order of features & step definitions/specs in ruby apps? (rails)

I am new to rails, cucumber and rspec. To help learn all three, I've started building a realistic application that requires login.
I would appreciate a little guidance as to where to start and confirmation I am on the right path.
I started with 2 features files. However, I have stopped at this stage as I'm wondering whether the 'login' feature (although a core aspect of the app as they can't do anything without being logged in) should come after the other assets and models, such as the things they manage when they are logged in.
So, which would come first? Features for the login or features for the models they manage?
example feature files:
Feature: User loads application
As a user
I want be able to load the application
So that I can manage my files
Scenario: Load application
Given I am not yet using the application
When I visit the application
Then I should see "Welcome to app"
login feature file:
Feature: User logs in
As a user
I want be able to login
So that I can manage my private files
Scenario: Successful login
Given the user "Username" has an account
When they login
Then they should see "You have logged in successfully"
Should I have started with a feature that they will actually use as the point of the app?
The order in which you implement features is a business decision. Whether you start with the login process or another feature depends on the business value each feature carries.
To help you find out where to start, you'll need to ask questions to the stakeholders. Here are a few examples:
Could we build feature A without user authentication?
Do we absolutely need user authentication at this point?
Let's consider we have resources to build only one single feature, what would be the most valuable one right now: login or feature A?
Building feature A before authentication can be a good strategy, as you'll be able to expose the feature to test users and improve on it earlier. Or, it could make no sense at all on your specific project and you'd want authentication to be ready before anything else.
Now, to comment on your particular scenarios, the style your using is pretty good.
I have the feeling (I might be wron) the user loads application feature is not really useful though. As a user, do you care about a "welcome to app" message? This scenario looks like a pre-functional setup test, something you'd like to have as a developer to kick off the development process. But it does not seem (again I might be wrong) to tell anything useful about the behaviour of the application.
This could be encapsulated behind a Cucumber feature describing some real expected behaviour of your systm (like the login process or adding items to a cart or reading blog posts, whatever is relevant to your domain).