Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
Can anyone post good test script templates(MSExcel)?
-- For Software Testing Project
thanks
Test Case ID - An unique ID to identify the test case
Precondition - Specify any precondition required to start the test case
Test Case Description - A Brief description explaining the purpose of the test case or the feature that is under test
Test Steps - Explain in detail all the necessary test steps required to be done to execute the test case
Expected Behavior - Clearly mention what is the expected behavior captured in the requirements
Author - Name of the test case owner
Requirement Origin - Feature name
Result - Pass / Fail / Not Run
Bug / Defect ID - To map the failed test cases
Remarks - Any comments
1.Level
2.FD Reference
3.Requirement ID
4.Test Type
5.Test Case Name
6.Test Case Number
7.Action
8.Expected Result
9.Outcome
10.Comments
11.Application
12.Release Scope
13.Critical
This file might help you.. This is the template for functionality testing
Test Case Id :Serial no assigned to test case
Purpose :Brief idea about case
Test Created By :Name of test creator
Test Environment: Software or hardware in which the test case is executed
Prerequisites :Conditions that should be fulfilled before the test is performed
Test Procedure :Steps to be performed in test
Test Data :Inputs, variables and data
Expected Result :LWhat the program should do
Actual Result :What is actually done
Verdict : Pass/Fail(Status of the test)
Comments :Notes on the procedure
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 9 months ago.
Improve this question
While system update from hac, we have three options
Update running system
Create essential data
localised type
Can anyone please explain what’s the use of all these three fields and why do we prefer unchecking “create essential data” most of the times?
A couple of links related to what essential data is:
https://help.sap.com/docs/SAP_COMMERCE/4c33bf189ab9409e84e589295c36d96e/8ad2f0a7866910149c31803942c91149.html?locale=en-US
https://help.sap.com/docs/SAP_COMMERCE/3fb5dcdfe37f40edbac7098ed40442c0/9236d781bd6a4330ad12dbc3b8880e77.html?locale=en-US
What do those 3 items do:
Update DB schema + type meta data in the DB for this Hybris environment
Load/reload the configured essential/core data sets into the DB
Load localisation file contents into the DB: localisation for types/attributes for example
In my view the essential/core data should always be safe to load during a system update, including in production. It is intended to be items that are essential for correct operation of the system & should not vary.
If there are items in the essential data that are being updated at runtime & essential data overwrites that - you either have incorrectly assigned some imports to essential data (instead of project/sample data), or you have somebody doing runtime stuff that they should not. Data that is intended for runtime maintenance should be in project/sampledata (which can be viewed as a starting point data set for the lower environments such as dev) - these data sets generally should not be run during an update, especially in production.
The create essential data is used for creating essential data that is the data required for the basic setup of the system and includes entities like countries, currencies, etc.
Rest of the data specific to the project should be categorized as project data.
This question already has an answer here:
Karate api testing - I would like to mask param values
(1 answer)
Closed 1 year ago.
I have some sensitive information in my test scripts, while executing the tests those are printing in the console log do I would like to mask console log for a specific scenario alone.
Please let me know if possible. I have looked at the example given in github but it doesn't help much as it's not clear.
Yes, please refer the documentation here: https://github.com/intuit/karate#report-verbosity
And if you use the tag #report=false for a Scenario (or even Feature) it should hide the logs only for that one.
If the above two suggestions don't help - please assume that what you want is NOT supported and either contribute code, or look for another tool - thanks.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
As the title states – instead of printing the exception, is it good practice to execute code in the except clause, which solves the error raised in the try clause?
For example, I'm creating a wrapper for Mininet, which creates some network topology. However, if the previous instance of the network topology isn't stopped, the creation fails, and the previous network must be cleaned up before the creation can succeed. This is done by executing the Mininet CLI command sudo mn -c. See the code below.
class MininetWrapper:
def __init__(self):
try:
self.net = Mininet(topo=<topology>, controller=<controller>)
except:
os.system('sudo mn -c')
self.net = Mininet(topo=<topology>, controller=<controller>)
self.net.start()
If the above is not good practice, please suggest a better method.
Executing code, sure. Blindly excepting all exceptions, almost definitely not. Rerunning the same code, probably a better way.
IMO except clauses are for when things aren't as you expect, but you don't want the system to suddenly fail. Instead you want to handle the error correctly.
In your case, one of the things you expect to happen is wanting to create an instance of this class when the previous network topology hasn't been stopped. So you should have the allowance for this already, and then have an except clause when something unexpected happens.
If you never what to have the previous thing running, why not always clean up the previous network? I looks like the API has a function for this already.
I would do something like:
class MininetWrapper:
def __init__(self):
Cleanup.cleanup()
self.net = Mininet(topo=<topology>, controller=<controller>)
self.net.start()
Notice I'm not catching any error because I don't expect anything to be wrong. If something is wrong now, I want the program to raise it.
Of course you can !
In fact, this is not "good practice" but just normal : except is made for handling and correcting exceptions...
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I am new to writing use cases.I heard that Use cases are non-technical expressions .
I have the following task for which i have to write Use case.
(I reduced the requirement for your understanding)
Registered Customer of ABC company logged in to the system with credentials to retrieve
the complete Address of particular service provider.He searches the service provider on TextBox.The System communcates with database and displays the result on monitor.
I am technical guy,
I have to write use case to explain the behavior of the system to the client.
I have written Use case as follows :
Use case Name: Address Locating System
Primary Actor: Customer
Stakeholder: ABC Company
Precondition: Customer Successfully Logged in to the system
Success Scenarios:
Customer Enter the search term in the box provided.
System searches the search terms for matches.
System Supplies the address to the Customer.
Extension Point: Client is informed when no successful match
Post condition: None
Questions.
Is the Use Case described above, correct?
Do really tech people need to write Use cases?
Whenever I need to write a Use Case, I pick up my copy of UML Distilled and use its suggested format. There are variations in the formats, so this isn't the only way. In any case it's a good reference to have on your desk. You might also check out Writing Effective Use Cases; I haven't read that one, though.
If you'd like a free example, see:
http://ontolog.cim3.net/cgi-bin/wiki.pl?UseCasesMartinFowlerSimpleTextExample
I might avoid the "in the box provided" bit - that's an implementation detail that might change. I might also change 2 to just "System searches for matches."
And yes, technical people do need to write Use Cases readable by non-technical domain experts.
I would say that this is your use case:
Registered Customer of ABC company
logged in to the system with
credentials to retrieve the complete
Address of particular service
provider.He searches the service
provider on TextBox.The System
communcates with database and displays
the result on monitor.
There is no need to do all the formatting, special headings, numbering etc. Give it a title and you are done. For presentation to a client,
I'd use use case diagrams, and not show even this amount of detail unless asked.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
While Scrum is easy in theory and hard in practice, I wanted to hear your definition of Done; i.e. what are the gates (unit test, code coverage > 80%, code reviews, load tests, perf.test, functional tests, etc.) your product has to go through before you can label the product "Done"
We at TargetProcess use the following definition of Done for user story:
Short Spec created
Implemented/Unit Tests created
Acceptance Tests created
100% Acceptance tests passed
Product Owner demo passed
Known bugs fixed
I'd say it is up to your team to decide. Talk with the product owner. Ideally done would be when a story is in Production and being used. However, there is a time gap between when a story is development complete and in Live. Makes it hard to track how long a story took to develop.
In my team, our definition of done is, when the developer completes a story,and does a "show and tell" to the rest of the team(testers, product owner), and if everyone is happy it goes into the subversion trunk.
Further testing is done off a automated build from trunk.
In a perfect world, the product shall be in a shippable state at the end of every iteration.
Now this actually depends on your product, your market, your customers and might not be possible.
If you cannot achieve this, then the next planning horizon apply: the release.
The Team as a whole should decide what is required to ship the product and plan accordingly.
What helps here is to define "done" at the task level. Defining done here is much more simple: one task is done when you can start another one: everything is tested, integrated. The Team can alo define this state: documented, reviewed, included in automatic build, no known problem, accpeted by On-Site Customer ...
Having all your tasks really "done", Having all tour backlog items (or User stories, whateveryou call them) realy "done" allow to be "done" at every iteration, which helps preserving the product in a shippable or deployable state.
There are three nice articles by Mitch Lacey, Dhaval Panchal and Mayank Gupta on this on the ScrumAlliance website.
EDIT: Basically the whole point is that done is defined on a project-by-project basis by the team. The basic need is to agree on the definition, not what the definition is.
Everything that will make your "stabilization period" (ie work required between the code freeze and the release to the client) shorter.